| 2.1 | Approval of the agenda | |
|---|---|---|
| R2-2109300 | Agenda for RAN2#116-e | Chairman |
| 2.2 | Approval of the report of the previous meeting | |
| R2-2109301 | RAN2#115-e Meeting Report | MCC |
| 2.4 | Others | |
| R2-2111401 | Handling of mobility and dual connectivity in mixed PNI-NPN/PLMN cell scenarios | R3 (Qualcomm Incorporated) |
| R2-2111402 | Clarification for SgNB trigger SCG release in Rel-15 in TS 37.340 | R3 (ZTE, NEC, Ericsson, Huawei) |
| R2-2111403 | Clarification for SgNB trigger SCG release in Rel-16 in TS 37.340 | R3 (ZTE, NEC, Ericsson, Huawei) |
| R2-2111404 | Correction on SN-initiated SN Release | R3 (Google) |
| R2-2111630 | Delegates work overload and organizational enhancements | Chairman |
| 3 | Incoming liaisons | |
| R2-2109309 | LS on Guidelines on Port Allocation for New 3GPP Interfaces (C4-214848; contact: Huawei) | CT4 |
| R2-2110295 | Location Services: Drones (LI(21)P58020r1; contact: Rogers) | ETSI TC LI |
| 4.1 | NB-IoT corrections Rel-15 and earlier | |
| R2-2110471 | Correction to NB-IoT measurements | Huawei, HiSilicon |
| R2-2111391 | [AT116-e][301][NBIOT R15R16] NB-IoT minor corrections (Huawei) | Huawei |
| 4.2 | eMTC corrections Rel-15 and earlier | |
| R2-2109514 | Summary of discussion on missing scheduling restrictions of positioning SI messages for eMTC | Lenovo, Motorola Mobility |
| R2-2109515 | Addition of scheduling restrictions of positioning SI messages for eMTC | Lenovo, Motorola Mobility |
| R2-2109516 | Addition of scheduling restrictions of positioning SI messages for eMTC | Lenovo, Motorola Mobility |
| R2-2111406 | [AT116-e][401][eMTC R15] Scheduling restrictions of positioning SI messages (Lenovo) | Lenovo |
| R2-2111408 | Addition of scheduling restrictions of positioning SI messages for eMTC | Lenovo, Motorola Mobility |
| R2-2111409 | Addition of scheduling restrictions of positioning SI messages for eMTC | Lenovo, Motorola Mobility |
| 4.5 | Other LTE corrections Rel-15 and earlier | |
| R2-2109828 | Addition of missing TEI15 features | Lenovo, Motorola Mobility (Rapporteur) |
| R2-2109829 | Addition of missing TEI15 features and other corrections | Lenovo, Motorola Mobility (Rapporteur) |
| R2-2109830 | Corrections to HSDN cell reselection enhancement | Lenovo, Motorola Mobility |
| R2-2109831 | Corrections to HSDN cell reselection enhancement | Lenovo, Motorola Mobility |
| R2-2111148 | Correction to application layer measurement and reporting | Google Inc. |
| R2-2111149 | Correction to application layer measurement and reporting | Google Inc. |
| R2-2111315 | Addition of missing TEI15 features | Lenovo, Motorola Mobility (Rapporteur) |
| R2-2111316 | Addition of missing TEI15 features and other corrections | Lenovo, Motorola Mobility (Rapporteur) |
| 5.3.1 | MAC | |
| R2-2109457 | Correction to SR procedure with UL skipping | Qualcomm Incorporated |
| R2-2109458 | Correction to SR procedure with UL skipping | Qualcomm Incorporated |
| 5.3.2 | RLC PDCP SDAP | |
| R2-2111027 | On association between RLC entities and PDCP entity | Huawei, HiSilicon |
| 5.4.1 | NR RRC | |
| R2-2111563 | [AT116-e][001][NR15] Connection Control (ZTE) | ZTE Corporation |
| 5.4.1.1 | Connection control | |
| R2-2109404 | Discussion on T302 | OPPO |
| R2-2109405 | Corrections on T302 | OPPO |
| R2-2109406 | Corrections on T302(R16) | OPPO |
| R2-2109791 | Delta signalling of dedicated channel bandwidth | Nokia, Nokia Shanghai Bell |
| R2-2110454 | Correction on BWP switch for TDD | ZTE Corporation, Sanechips, Ericsson |
| R2-2110455 | Correction on BWP switch for TDD(R16) | ZTE Corporation, Sanechips, Ericsson |
| R2-2110456 | Correction on srb-ToAddModList | ZTE Corporation, Sanechips |
| R2-2110457 | Correction on srb-ToAddModList(R16) | ZTE Corporation, Sanechips |
| R2-2110458 | Correction on vrb-ToPRB-Interleaver | ZTE Corporation, Sanechips |
| R2-2110459 | Correction on vrb-ToPRB-Interleaver(R16) | ZTE Corporation, Sanechips |
| R2-2110513 | Consideration for ServingCellConfigCommon | Qualcomm Incorporated |
| R2-2110701 | [Post115-e][054][NR15] Common Fields Dedicated Signalling (Ericsson) | Ericsson |
| R2-2110783 | UAI retransmission upon RRC reconfiguration (36.331) | Ericsson |
| R2-2110784 | UAI retransmission upon RRC reconfiguration (36.331) | Ericsson |
| R2-2110785 | UAI retransmission upon RRC reconfiguration (38.331) | Ericsson |
| R2-2110786 | UAI retransmission upon RRC reconfiguration (38.331) | Ericsson |
| R2-2111457 | Summary of [AT116-e][009][NR16] Connection Control II | Ericsson |
| 5.4.1.2 | Inter-Node RRC messages | |
| R2-2110460 | Correction on reestablishmentInfo | ZTE Corporation, Sanechips |
| R2-2110461 | Correction on reestablishmentInfo(R16) | ZTE Corporation, Sanechips |
| R2-2110462 | Correction on reestablishmentInfo | ZTE Corporation, Sanechips |
| R2-2110463 | Correction on reestablishmentInfo(R16) | ZTE Corporation, Sanechips |
| R2-2111458 | Summary of [AT116-e][002][NR15] RRC Inter Node Other and LTE | Ericsson |
| R2-2111564 | Correction on reestablishmentInfo | ZTE Corporation, Sanechips |
| R2-2111565 | Correction on reestablishmentInfo(R16) | ZTE Corporation, Sanechips |
| 5.4.1.3 | Other | |
| R2-2109370 | Association between serving cell and measurement object (R5-215762; contact: HiSilicon) | RAN5 |
| R2-2109885 | Clarification on density configuration in CSI-RS based measurement | ZTE Corporation, Sanechips |
| R2-2109886 | LS to RAN4 on density configuration in CSI-RS based measurement | ZTE Corporation, Sanechips |
| R2-2110022 | L3 Filtering (filterCoefficient) Clarification | Apple, Ericsson |
| R2-2110250 | Corrections on the configuration of serving cells | NEC |
| R2-2110251 | Corrections on the configuration of serving cells | NEC |
| R2-2110696 | Miscellaneous non-controversial corrections Set XII | Ericsson |
| R2-2110796 | Draft LS to RAN4 on L3 filter configuration | Apple, Ericsson |
| R2-2111182 | Discussion on association between serving cell and measurement object | MediaTek Inc. |
| R2-2111265 | Discussion on servingCellMO | Huawei, HiSilicon |
| R2-2111473 | Reply LS on association between serving cell and measurement object | RAN2 |
| R2-2111590 | LS to RAN4 on L3 filter configuration | RAN2 |
| R2-2111608 | Miscellaneous non-controversial corrections Set XII | Ericsson |
| 5.4.2 | LTE changes | |
| R2-2110939 | Correction to nas-Container | Sequans Communications |
| R2-2110942 | Correction to nas-Container | Sequans Communications |
| 5.4.3 | UE capabilities | |
| R2-2109310 | Reply LS on the Intra-band and Inter-band (NG)EN-DC/NE-DC Capabilties (R1-2108378; contact: ZTE) | RAN1 |
| R2-2110565 | Report for [Post115-e][087][NR15] Simultaneous Rx/Tx cap finer granularity (NTT DOCOMO) | NTT DOCOMO, INC. |
| R2-2110566 | Simultaneous Rx/Tx UE capability per band pair | NTT DOCOMO, INC. |
| R2-2110567 | Simultaneous Rx/Tx UE capability per band pair | NTT DOCOMO, INC. |
| R2-2110568 | Simultaneous Rx/Tx UE capability per band pair | NTT DOCOMO, INC. |
| R2-2110569 | Simultaneous Rx/Tx UE capability per band pair | NTT DOCOMO, INC. |
| R2-2110570 | Draft LS on dynamic resource coordination for simultaneous Rx/Tx UE capability | NTT DOCOMO, INC. |
| R2-2110571 | Remaining issues on simultaneous Rx/Tx capability per band pair | NTT DOCOMO, INC. |
| R2-2110969 | Clarification on intraAndInterF-MeasAndReport capability | Huawei, HiSilicon |
| R2-2110970 | Clarification on intraAndInterF-MeasAndReport capability | Huawei, HiSilicon |
| R2-2110971 | Miscellaneous corrections for Rel-15 UE capabilities | Huawei, HiSilicon |
| R2-2110972 | Miscellaneous corrections for Rel-15 UE capabilities | Huawei, HiSilicon |
| R2-2111493 | Report for [AT116-e][037][NR15] Simultaneous Rx/Tx UE capability per band pair (NTT DOCOMO) | NTT DOCOMO, INC. |
| R2-2111494 | Simultaneous Rx/Tx UE capability per band pair | NTT DOCOMO, INC. |
| R2-2111495 | Simultaneous Rx/Tx UE capability per band pair | NTT DOCOMO, INC. |
| R2-2111496 | Simultaneous Rx/Tx UE capability per band pair | NTT DOCOMO, INC. |
| R2-2111497 | Simultaneous Rx/Tx UE capability per band pair | NTT DOCOMO, INC. |
| R2-2111579 | Summary of [AT116-e][003][NR15] UE Capabilities I | Huawei, HiSilicon |
| R2-2111581 | Clarification on intraAndInterF-MeasAndReport capability | Huawei, HiSilicon |
| R2-2111582 | Clarification on intraAndInterF-MeasAndReport capability | Huawei, HiSilicon |
| 5.5 | Positioning corrections | |
| R2-2111126 | Correction on LPP message delivery | vivo |
| R2-2111127 | Correction on LPP message delivery | vivo |
| R2-2111548 | Summary of [AT116-e][614][POS] AI 5.5 CRs | vivo |
| 6.1.1 | Organisational | |
| R2-2109344 | LS on downlink unmapped QoS flows (R3-214453; contact: CATT) | RAN3 |
| R2-2111068 | Discussion on downlink unmapped QoS flows | CATT, Huawei, HiSilicon |
| R2-2111069 | Draft Reply LS on downlink unmapped QoS flows | CATT |
| R2-2111466 | Report of ?[AT116-e][004][NR16] CPUP split reply LS (CATT)? | CATT |
| R2-2111467 | Draft Reply LS on downlink unmapped QoS flows | CATT |
| R2-2111492 | Reply LS on downlink unmapped QoS flows | RAN2 |
| 6.1.2 | Stage 2 corrections | |
| R2-2111531 | Offline 005 on Stage 2 | Nokia (Rapporteur) |
| 6.1.2.1 | TS 3x.300 | |
| R2-2109535 | Corrections to early measurements in RRC INACTIVE | Samsung Electronics Co., Ltd |
| R2-2109952 | Miscellaneous Corrections | Nokia (Rapporteur), Nokia Shanghai Bell, Sharp |
| R2-2110732 | Correction to 38300 on 2step CFRA configuration | ZTE Corporation, Sanechips |
| R2-2111470 | Miscellaneous Corrections | Nokia (Rapporteur), Nokia Shanghai Bell, Sharp, Samsung |
| 6.1.2.2 | TS 37.340 | |
| R2-2109459 | Correction on conditional reconfiguration for PSCell | Google Inc., Intel Corporation, ZTE |
| R2-2110527 | Corrections on SCG/MCG failure handling | ZTE Corporation, Sanechips |
| 6.1.3.1 | MAC | |
| R2-2109533 | Corrections to LCP for truncated SCell BFR MAC CE | Samsung Electronics Co., Ltd |
| R2-2109650 | Clarifying the handling of Multi-TB CGs in MAC | CATT |
| R2-2109921 | Handling of One-shot HARQ feedback for NR-U | Qualcomm Incorporated |
| R2-2109948 | Clarification on Duplication MAC CE | Samsung |
| R2-2110244 | Start of DRX RTT timer for one-shot HARQ feedback | Lenovo, Motorola Mobility |
| R2-2110763 | Correction on downlink pathloss reference for 2-step RACH | Qualcomm Incorporated |
| R2-2110946 | Discussion on MSGA grant overlapping with another UL grant for a HARQ process | LG Electronics Deutschland |
| R2-2110948 | DRX HARQ RTT timer for one-shot HARQ feedback | LG Electronics Deutschland |
| R2-2110949 | CR to DRX HARQ RTT timer for one-shot HARQ feedback | LG Electronics Deutschland |
| R2-2111231 | Correction to MsgA and Msg3 retransmission overlapping with another bundle retransmission | Huawei, HiSilicon |
| R2-2111440 | Clarification on Duplication MAC CE | Samsung |
| R2-2111576 | Corrections to LCP for truncated SCell BFR MAC CE | Samsung Electronics |
| R2-2111624 | Report of [AT116-e][006][NR1516] MAC | Qualcomm Incorporated |
| 6.1.3.3 | PDCP | |
| R2-2109945 | Clarification on the ciphering of LTE EHC header | Samsung |
| R2-2109946 | CR for the ciphering of LTE EHC header (Rel-15) | Samsung |
| R2-2109947 | CR for the ciphering of LTE EHC header (Rel-16) | Samsung |
| R2-2110757 | Clarification on joint EHC and RoHC operation | MediaTek Inc. |
| R2-2110758 | Clarification on joint EHC and RoHC operation | MediaTek Inc. |
| R2-2111480 | CR for the ciphering of LTE EHC header (Rel-15) | Samsung |
| R2-2111481 | CR for the ciphering of LTE EHC header (Rel-16) | Samsung |
| R2-2111572 | [AT116-e][007][NR1516] PDCP (Samsung) | Samsung |
| R2-2111648 | Clarification on Security Coverage | Samsung |
| R2-2111649 | Clarification on Security Coverage | Samsung |
| 6.1.4.1.1 | Connection control | |
| R2-2109314 | LS to RAN2 on default value for rb-Offset (R1-2108436; contact: Ericsson) | RAN1 |
| R2-2109340 | LS on inter-MN RRC resume without SN change (R3-214360; contact: Qualcomm) | RAN3 |
| R2-2109346 | LS on UP security policy updated by intra-cell handover (R3-214464; contact: China Telecom) | RAN3 |
| R2-2109792 | Inter-MN RRC resume without SN change | Nokia, Nokia Shanghai Bell |
| R2-2109864 | Correction of default value of rb-offset | Ericsson |
| R2-2109887 | Discussion on inter-MN RRC resume without SN change | ZTE Corporation, Sanechips |
| R2-2109888 | Reply LS on inter-MN RRC resume without SN change | ZTE Corporation, Sanechips |
| R2-2110012 | Reply LS on Inter-MN RRC resume without SN change | Qualcomm Incorporated |
| R2-2110421 | CPC handling during recovery procedure | Lenovo, Motorola Mobility |
| R2-2110423 | CPC handling during recovery procedure | Lenovo, Motorola Mobility |
| R2-2110523 | Discussion on the Timing Reference of PSCell SMTC Configuration | vivo |
| R2-2110524 | Clarification on the Timing Reference of PSCell SMTC Configuration | vivo |
| R2-2110525 | Define the UE capability for PSCell SMTC configuration | vivo |
| R2-2110526 | Clarification on the Timing Reference of PSCell SMTC Configuration | vivo |
| R2-2110626 | Clarification of default value for rb-Offset | Nokia, Nokia Shanghai Bell |
| R2-2110631 | Correction on condRRCReconfig field description | Huawei, HiSilicon |
| R2-2110632 | Correction on condReconfigurationToApply field description | Huawei, HiSilicon |
| R2-2110682 | Support of inter-MN RRC resume without SN change | Ericsson |
| R2-2110683 | [Draft] Reply LS on inter-MN RRC resume without SN change | Ericsson |
| R2-2110684 | Clarification on restore MCG and SCG in case of RRC resume | Ericsson |
| R2-2110685 | Discussion on UP security policy updated by intra-cell handover | Ericsson |
| R2-2110686 | [Draft] Reply LS on UP security policy updated by intra-cell handover | Ericsson |
| R2-2110756 | Correction to need code for drb-ContinueEHC-DL and drb-ContinueEHC-UL | MediaTek Inc. |
| R2-2110879 | Correction on pucch-SpatialRelationInfoId-v1610 | Huawei, HiSilicon |
| R2-2110945 | Inter-MN RRC resume without SN change - RAN2 aspects | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R2-2111036 | Discussion on Ls on Inter-MN RRC resume without SN change | vivo |
| R2-2111037 | Discussion on Ls on UP security update | vivo |
| R2-2111070 | Modification of reportConfig for conditional reconfiguration | Xiaomi Communications |
| R2-2111071 | Modification of reportConfig for conditional reconfiguration | Xiaomi Communications |
| R2-2111080 | Conditional reconfiguration issues for modification of measId | Xiaomi Communications |
| R2-2111173 | Conditional Handover with Two Triggering Events | MediaTek Inc. |
| R2-2111178 | Conditional Handover with Two Trigger Events | MediaTek Inc. |
| R2-2111200 | Discussion on UP security policy updated by intra-cell handover | China Telecommunications |
| R2-2111286 | Report of email discussion [AT116-e][008][NR16] Connection Control I (Huawei) | Huawei |
| R2-2111478 | Correction for default value of rb-offset | Ericsson |
| R2-2111515 | Correction on pucch-SpatialRelationInfoId-v1610 | Huawei, HiSilicon |
| R2-2111527 | Reply LS on UP security policy update | RAN2 |
| R2-2111549 | Correction to need code for drb-ContinueEHC-DL and drb-ContinueEHC-UL | MediaTek |
| R2-2111591 | Reply LS on inter-MN RRC resume without SN change | RAN2 |
| R2-2111593 | Correction on condRRCReconfig field description | Huawei, HiSilicon |
| R2-2111594 | Correction on condReconfigurationToApply field description | Huawei, HiSilicon |
| R2-2111626 | Correction on pucch-SpatialRelationInfoId-v1610 | Huawei, HiSilicon |
| 6.1.4.1.2 | RRM and Measurements | |
| R2-2110982 | Discussion on inter-frequency no gap measurement in NR-DC | Huawei, HiSilicon |
| R2-2111468 | CR on inter-frequency gapless measurement | Huawei, HiSilicon |
| R2-2111505 | Report of [Offline-011][NR16] RRC Measurements Other and LTE (Ericsson) | Ericsson |
| 6.1.4.1.5 | Other | |
| R2-2109445 | Correction on msgA-SubcarrierSpacing | vivo, Samsung |
| R2-2110579 | Correction on description of absoluteFrequencySSB | ZTE Corporation, Sanechips |
| R2-2110580 | Correction on description of cp-ExtensionC2 and cp-ExtensionC3 | ZTE Corporation, Sanechips |
| R2-2110697 | Miscellaneous non-controversial corrections Set XII | Ericsson |
| R2-2110794 | Extension of pathlossReferenceRSs | MediaTek Inc. |
| R2-2110878 | Correction on supportNewDMRS-Port-r16 capability | Huawei, HiSilicon |
| R2-2111538 | Correction on description of absoluteFrequencySSB | ZTE Corporation, Sanechips |
| R2-2111607 | Extension of pathlossReferenceRSs | MediaTek Inc. |
| R2-2111609 | Miscellaneous non-controversial corrections Set XII | Ericsson |
| R2-2111622 | Correction on msgA-SubcarrierSpacing | vivo, Samsung |
| R2-2111627 | Correction on supportNewDMRS-Port-r16 capability | Huawei, HiSilicon |
| R2-2111656 | Correction on description of absoluteFrequencySSB | ZTE Corporation, Sanechips |
| 6.1.4.2 | LTE changes | |
| R2-2110725 | Correction on sending SCG Overheating in EN-DC | Nokia, Nokia Shanghai Bell |
| R2-2111079 | SCG Overheating termination indication in EN-DC | Qualcomm Incorporated, Ericsson |
| R2-2111610 | SCG Overheating termination indication in EN-DC | Qualcomm Incorporated, Ericsson |
| 6.1.4.3 | UE capabilities | |
| R2-2109331 | Reply LS on Two PUCCH Capability (R1-2108657; contact: Qualcomm) | RAN1 |
| R2-2109395 | Discussion on capability for DAPS | OPPO |
| R2-2110023 | Correction on R16 UE capability of supportedSINR-meas-r16 | Apple |
| R2-2110024 | Correction on R16 UE capability of supportedSINR-meas-r16 | Apple |
| R2-2110231 | Add the missing capabilities for SON and MDT | CMCC |
| R2-2110420 | Discussion on the handover delay due to SCell activation | OPPO |
| R2-2110483 | Adding UE capability of UL MIMO coherence for UL Tx switching | Huawei, HiSilicon, China Telecom, Apple |
| R2-2110484 | Adding UE capability of UL MIMO coherence for UL Tx switching | Huawei, HiSilicon, China Telecom, Apple |
| R2-2110563 | Keeping or removing diffSCS-DAPS | Ericsson |
| R2-2110627 | Clarification regarding CodebookVariantsList-r16 | Nokia, Nokia Shanghai Bell |
| R2-2110628 | Clarification regarding CodebookVariantsList-r16 | Nokia, Nokia Shanghai Bell |
| R2-2110629 | Clarification regarding CodebookVariantsList-r16 | Nokia, Nokia Shanghai Bell |
| R2-2110633 | Discussion on some issues for DAPS | Huawei, HiSilicon |
| R2-2110777 | Support of UL Tx switching and relation with further enhancements | Ericsson |
| R2-2110780 | UL MIMO coherence for Tx switching between two carriers | Ericsson |
| R2-2110973 | Miscellaneous corrections for Rel-16 UE capabilities | Huawei, HiSilicon |
| R2-2111058 | Clarification on UL MIMO layer reporting for 1Tx-2Tx switching | Huawei, HiSilicon, China Telecom, Apple |
| R2-2111271 | Correction on two HARQ-ACK codebooks capability | Qualcomm Incorporated |
| R2-2111533 | Add the missing capabilities for SON and MDT | CMCC |
| R2-2111569 | LS on inter-frequency DAPS handover with overlapping bandwidth | OPPO |
| R2-2111570 | Correction on DAPS capability | OPPO |
| R2-2111574 | Summary of [AT116-e][012][NR16] UE capabilities I | OPPO |
| R2-2111577 | Correction on R16 UE capability of supportedSINR-meas-r16 | Apple |
| R2-2111580 | Summary of [AT116-e][013][NR16] UE capabilities II | Huawei, HiSilicon |
| R2-2111623 | Summary of [AT116-e][012][NR16] UE capabilities I | OPPO |
| R2-2111651 | Clarification on UL MIMO layer reporting for 1Tx-2Tx switching | Huawei, HiSilicon, China Telecom, Apple |
| 6.1.4.4 | Idle/inactive mode procedures | |
| R2-2109369 | Reply LS on power class and P-max for IAB-MT cell selection (R4-2115704; contact: CATT) | RAN4 |
| R2-2109580 | Correction for TS 38.304 on power class for cell selection of IAB | CATT,Huawei, HiSilicon |
| R2-2109581 | Correction for TS 36.304 on power class for cell selection of IAB | CATT,Huawei,HiSilicon |
| R2-2109774 | Correction on RRM relaxation of higher priority frequencies | OPPO |
| R2-2110405 | RRM relaxation | Ericsson |
| R2-2110406 | Addressing inconsistency for RRM measurement rules | Ericsson, CATT |
| R2-2110407 | DRAFT LS on highPriorityMeasRelax parameter | Ericsson |
| R2-2111540 | Summary of [AT116-e][014][NR16] Idle Inactive (CATT) | CATT (Rapporteur) |
| 6.2.1 | General and Stage-2 corrections | |
| R2-2109311 | LS to RAN2 on mode 2 resource reservation period (R1-2108393; contact: Huawei) | RAN1 |
| R2-2109315 | Reply LS on Resource Reselection Trigger sl-reselectAfter (R1-2108438; contact: Apple) | RAN1 |
| 6.2.2 | Control plane corrections | |
| R2-2109596 | Miscelleneous CR on 38.331 | Huawei, HiSilicon |
| R2-2109628 | Mode 2 Resource Reservation Period | Qualcomm Finland RFFE Oy |
| R2-2109629 | Discussion on mode 2 resource reservation period | Qualcomm Finland RFFE Oy |
| R2-2109630 | CR to 38.331 on ResourceReservationPeriodList | Qualcomm Finland RFFE Oy |
| R2-2109804 | Further issues on multiplexing sidelink logical channels with HARQ feedback enabled vs. disabled | Nokia, Nokia Shanghai Bell |
| R2-2109806 | Correction of IE sl-HARQ-FeedbackEnabled | Nokia, Nokia Shanghai Bell |
| R2-2110269 | Correction on SL RLC parameter configuration | vivo |
| R2-2110611 | Corrections on RRC parameter sl-ResourceReservePeriodList | CATT |
| R2-2110795 | Inclusion of 0 ms resource reservation period in sl-ResourceReservePeriodList | MediaTek Inc. |
| R2-2110830 | Correction on power control parameter | ZTE Corporation, Sanechips |
| R2-2110831 | Correction on TS 38.331 from the latest RAN1 decision | ZTE Corporation, Sanechips |
| R2-2111230 | Review report for CP contributions | Huawei, HiSilicon |
| R2-2111424 | Miscellaneous corrections on TS 38.331 | Huawei, HiSilicon, Qualcomm, CATT, MediaTek, ZTE, Sanechips, Nokia, Nokia Shanghai Bell, vivo |
| R2-2111425 | Summary [AT116-e][707][V2X/SL] Miscellaneous CR on 38.331 | Huawei, HiSilicon |
| 6.2.3 | User plane corrections | |
| R2-2109402 | Correction on resource reselection behavior and MCS selection | OPPO |
| R2-2109417 | Left issue on maxTransNum | OPPO, Apple, Ericsson, Lenovo, Motorola Mobility |
| R2-2109418 | Correction on UL-SL prioritization | OPPO, Apple, MediaTek, CATT |
| R2-2109534 | Corrections to Sidelink BWP operation | Samsung Electronics Co., Ltd |
| R2-2109597 | Correction on the dynamic sidelink grants | Huawei, HiSilicon |
| R2-2109598 | Clarification on the UL and NR SL prioritization | Huawei, HiSilicon |
| R2-2110058 | Correction on the usage of sl-ReselectAfter | Apple, OPPO, Qualcomm Incorporated, Huawei, HiSilicon |
| R2-2110152 | Clarification on exceptional pool configuration | LG Electronics France |
| R2-2110153 | Discussion on left issue related to sl-CG-MaxTransNumList | LG Electronics France |
| R2-2110154 | Review Report on MAC CRs | LG Electronics France |
| R2-2110159 | Miscelleneous CR on 38.321 | LG Electronics France |
| R2-2110160 | Miscelleneous CR on 36.321 | LG Electronics France |
| R2-2110161 | Corrections to prioritization for NR sidelink communication | LG Electronics Inc. |
| R2-2110446 | Correction to Window_Size for SLRB | Samsung |
| R2-2110610 | PDCP/RLC Entity Maintenance for SL-SRBs | CATT, APPLE, vivo, Huawei, HiSilicon, OPPO |
| R2-2110652 | Remaining issues on sl-MaxTransNum configuration and UE behaviour | vivo |
| R2-2110829 | Correction on TX parameters selection | ZTE Corporation, Sanechips |
| R2-2110832 | Correction on HARQ information indication | ZTE Corporation, Sanechips |
| R2-2111138 | Corrections on Parameter Definition of the Formula for Computing CG slots | CATT |
| R2-2111283 | Correction to Window_Size for SLRB | Samsung |
| R2-2111426 | Miscelleneous CR on 38.321 (Rapporteur CR) | LG Electronics Inc. |
| R2-2111427 | Summary [AT116-e][708][V2X/SL] Miscellaneous CR on 38.321 | LG Electronics Inc. (Rapporteur) |
| R2-2111428 | Correction on resource reselection behaviour | OPPO |
| R2-2111429 | Summary [AT116-e][709][V2X/SL] PDCP/RLC Entity Maintenance for SL-SRBs (CATT) | CATT |
| 6.3.1 | General and Stage 2 corrections | |
| R2-2109313 | LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#105-e (R1-2108427; contact: NTT DoCoMo, AT&T) | RAN1 |
| R2-2109333 | Reply LS on E-CID LTE measurement in Rel-15 measurements (R3-212802; contact: Huawei) | RAN3 |
| R2-2109679 | Updates based on RAN1 NR positioning features list | Intel Corporation |
| R2-2109680 | Updates based on RAN1 NR positioning features list | Intel Corporation |
| R2-2109681 | Updates based on RAN1 NR positioning features list | Intel Corporation |
| R2-2110169 | Correction to the alignement between stage2 and stage3 | Huawei, HiSilicon |
| R2-2110170 | Correciton to Event Reporting in RRC_IDLE | Huawei, HiSilicon |
| R2-2110728 | Corrections on defintions and scope of information transfer | Ericsson |
| R2-2111383 | Updates based on RAN1 NR positioning features list | Intel Corporation |
| R2-2111384 | Updates based on RAN1 NR positioning features list | Intel Corporation |
| R2-2111385 | Updates based on RAN1 NR positioning features list | Intel Corporation |
| R2-2111386 | Draft response LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#105-e | Intel |
| R2-2111387 | [AT116-e][616][POS] Updates for RAN1 positioning feature list (Intel) | Intel Corporation |
| R2-2111388 | Correction to the alignement between stage2 and stage3 | Huawei, HiSilicon |
| R2-2111389 | Summary of [AT116-e][619][POS] Stage 2 Rel-16 positioning CRs (Huawei) | Huawei, HiSilicon |
| R2-2111483 | Response LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#105-e | RAN2 |
| R2-2111486 | Alignment between stage 2 and Stage 3 specifications | Huawei, HiSilicon |
| R2-2111652 | Updates based on RAN1 NR positioning features list | Intel Corporation |
| R2-2111653 | Updates based on RAN1 NR positioning features list | Intel Corporation |
| R2-2111654 | Updates based on RAN1 NR positioning features list | Intel Corporation |
| 6.3.2 | RRC corrections | |
| R2-2110172 | Correction to posSRS capability associated with PRS-only TP | Huawei, HiSilicon |
| 6.3.3 | LPP corrections | |
| R2-2110173 | Correction to posSRS and PRS capability associated with PRS-only TP | Huawei, HiSilicon |
| R2-2111072 | Correction on BDS B2I clock model | Swift Navigation, Ericsson |
| R2-2111198 | Discussion on LPP segmentation in LCS message | vivo |
| R2-2111366 | Correction on BDS B2I clock model | Swift Navigation, Ericsson |
| R2-2111484 | Correction on BDS B2I clock model [Rel16BDS] | Swift Navigation, Ericsson |
| R2-2111655 | Correction on BDS B2I clock model [Rel16BDS] | Swift Navigation, Ericsson |
| 6.3.4 | MAC corrections | |
| R2-2110171 | Discussion on impacts of TA expiry and SR failure on uplink positoning | Huawei, HiSilicon |
| R2-2111272 | Discussion on impacts of TA expiry and SR failure on uplink positoning | Huawei, HiSilicon |
| R2-2111369 | Clarification on posSRS in MAC spec | Huawei, HiSilicon |
| 6.4.1 | General and stage-2 corrections | |
| R2-2109387 | LS Reply on QoS Monitoring for URLLC (S5-211350; contact: Intel) | SA5 |
| R2-2110634 | Draft Reply LS on QoS Monitoring for URLLC | Huawei |
| R2-2110852 | On reply LS to RAN3 on MDT Stage 2 and Stage 3 Alignment (reply LS to R3-207222) | Ericsson |
| R2-2111195 | TS 37.320 title update | Nokia, Nokia Shanghai Bell |
| R2-2111567 | Reply LS on MDT Stage 2 and Stage 3 Alignment (reply LS to R3-207222) | RAN2 |
| 6.4.3 | RRC corrections | |
| R2-2110002 | Clarification on Location for SCG Failure Report in 38.331 | CATT |
| R2-2110003 | Clarification on Location for SCG Failure Report in 36.331 | CATT |
| R2-2110004 | Clarification on RA report without 2 step RA | CATT |
| R2-2110078 | Correction on RA Resource Reporting | Apple, Ericsson |
| R2-2110079 | Addition of missing information into RA-InformationCommon-r16 | Apple, Ericsson |
| R2-2110252 | Corrections on the field descriptions of IEs for CEF-report and RLF-report request | NEC |
| R2-2110843 | On neighbor cell measurements associated to interFreqTargetInfo | Ericsson |
| R2-2110851 | On logging of neighbour PCI measurements based on interFreqTargetInfo | Ericsson |
| R2-2110853 | On neighbour CSI-RS measurements in RLF report | Ericsson |
| R2-2110855 | On User Consent related aspects | Ericsson |
| R2-2110858 | On Logging MHI report upon transition from RRC_CONNECTED to any cell selection state | Ericsson |
| R2-2110887 | Corrections to previousPCellID and timeConnFailure handling | Ericsson |
| R2-2111442 | SON-MDT changes agreed in RAN#116 meeting | Ericsson |
| R2-2111455 | SON-MDT changes agreed in RAN#116 meeting | Ericsson |
| R2-2111646 | SON-MDT changes agreed in RAN#116 meeting | Ericsson |
| 7.2 | Additional MTC enhancements for LTE | |
| R2-2109366 | Reply LS on RSS-based RSRQ (R4-2115425; contact: Huawei) | RAN4 |
| R2-2111208 | Removal of RSS based RSRQ measurements | Huawei, HiSilicon |
| R2-2111407 | [AT116-e][402][eMTC R15R16] RSS-based RSRQ measurements (Huawei) | Huawei |
| R2-2111410 | Removal of RSS based RSRQ measurements | Huawei, HiSilicon, Qualcomm Incorporated |
| R2-2111411 | Removal of RSS based RSRQ measurements | Huawei, HiSilicon, Qualcomm Incorporated |
| R2-2111412 | Introduction of a capability for support of RSS-based measurements in RRC_IDLE | Huawei, HiSilicon |
| 7.3 | Additional enhancements for NB-IoT | |
| R2-2110240 | Discussion on the issue for Random Access on multicarrier for NB-IoT | CMCC |
| R2-2110241 | Solving the issue for random access on multiCarrier in NB-IoT | CMCC |
| R2-2110472 | Correction to DL Multi-TB scheduling in NB-IoT | Huawei, HiSilicon |
| R2-2110762 | Solving the issue for random access on multiCarrier in NB-IoT | CMCC |
| R2-2111392 | Offline discussion on the issue for Random Access on multicarrier for NB-IoT | CMCC |
| R2-2111395 | Correction to DL Multi-TB scheduling in NB-IoT | Huawei, HiSilicon |
| 7.4 | LTE Other WIs | |
| R2-2109803 | Discard of received segments of RRC messages | Samsung |
| R2-2110805 | Miscellaneous corrections | Nokia (rapporteur), Qualcomm Incorporated |
| R2-2111136 | Correction on cellsTriggeredList | Samsung R&D Institute UK |
| R2-2111305 | Report from email discussion [AT116-e][205][LTE] Miscellaneous LTE CRs (Lenovo) | Lenovo |
| R2-2111317 | Miscellaneous corrections | Nokia (rapporteur), Qualcomm Incorporated |
| R2-2111318 | Discard of received segments of RRC messages | Samsung |
| 8.0 | Organizational | |
| R2-2110778 | Set Modify Release structure | Ericsson |
| R2-2110779 | Draft CR for SetModifyRelease structure (38.331) | Ericsson |
| R2-2110782 | Allowing FRx/xDD differentiation on UE capabilities | Ericsson, Samsung |
| R2-2111259 | Preparation for Rel-17 UE capability | Intel Corporation |
| R2-2111606 | Summary of offline 048 Rel-17 RRC SetModifyRelease | Ericsson |
| 8.1.1 | Organizational, Requirements, Scope and Architecture | |
| R2-2109376 | LS on latest progress and outstanding issues in SA WG2 (S2-2106833; contact: Huawei) | SA2 |
| R2-2109381 | Reply LS for the security issue of MBS interest indication (S3-213623; contact: Xiaomi) | SA3 |
| R2-2110630 | Open issue list for NR MBS | Huawei, HiSilicon |
| R2-2110954 | Correction of L2 architecture figure for multicast session | Nokia, Nokia Shanghai Bell |
| R2-2111238 | Reply LS on paging for multicast session activation notification (S2-2107994; contact: ZTE) | SA2 |
| R2-2111239 | LS on Multicast paging with TMGI (S2-2107995; contact: Qualcomm) | SA2 |
| R2-2111240 | LS on MBS data forwarding (S2-2107996; contact: Qualcomm) | SA2 |
| R2-2111244 | Reply LS on MBS broadcast service continuity and MBS session identification (S2-2108175; contact: Huawei) | SA2 |
| R2-2111414 | 38.321 running CR for NR MBS | OPPO |
| R2-2111441 | 38.304 running CR for NR MBS | CATT |
| R2-2111511 | Further reply on MBS broadcast service continuity | RAN2 |
| R2-2111605 | 38.300 Running CR for MBS in NR | CMCC, Huawei |
| R2-2111658 | 38.331 running CR for NR MBS | Huawei, HiSilicon |
| R2-2111659 | 37.324 Running CR for NR MBS | Samsung |
| R2-2111666 | 38.323 running CR for NR MBS | Xiaomi Communications |
| 8.1.2 | L2 Centric | |
| R2-2110319 | [Post115-e][092][MBS] Remaining User plane issues (Lenovo) | Lenovo, Motorola Mobility |
| R2-2111526 | Report of offline discussion: [AT116-e][050][MBS] UP continuation | Lenovo, Motorola Mobility |
| 8.1.2.1 | Multicast Service Continuity | |
| R2-2109420 | Open Issues on Mobility of Delivery Mode 1 | CATT, CBN |
| R2-2109421 | Discussion on Remaining Issues for PDCP and RLC in MBS | CATT |
| R2-2109548 | Mobility and Service continuity for NR Multicast | MediaTek Inc. |
| R2-2109589 | Multicast Service Continuity Aspects | Ericsson |
| R2-2109682 | PTP PTM switch and service continuity | MediaTek Inc. |
| R2-2109836 | Lossless PTM/PTP switching | InterDigital |
| R2-2109849 | L2 ARQ by PDCP for PTM | Futurewei, Qualcomm Inc., Intel, UIC, Kyocera, NEC, Samsung, Ericsson |
| R2-2109850 | PDCP Functionality during Mobility and PTM-PTP Switch | Futurewei |
| R2-2109902 | NR Multicast loss-less HO enhancements with service continuity | Qualcomm Inc |
| R2-2109949 | MBS Reliability | Nokia, Nokia Shanghai Bell |
| R2-2109954 | MBS Mobility | Nokia, Nokia Shanghai Bell |
| R2-2109955 | Draft LS on MBS mobility | Nokia |
| R2-2109993 | Remaining issues on MRB bearer type change | vivo |
| R2-2109995 | Service continuity for NR MBS | vivo |
| R2-2109996 | CHO and DAPS for NR MBS | vivo |
| R2-2110025 | PTM and PTP switch with MBS service continuity | Apple |
| R2-2110026 | Mobility with MBS service continuity | Apple |
| R2-2110116 | Handover from a MBS supporting Node to a non-MBS supporting Node | Sharp |
| R2-2110132 | Discussion on Multicast service continuity during mobility | Spreadtrum Communications |
| R2-2110205 | Remaining issues of multicast service continuity | Kyocera |
| R2-2110320 | Service continuity for handover from MBS supporting to MBS non supporting node | Lenovo, Motorola Mobility |
| R2-2110494 | Discussion on Multicast Service Continuity | Samsung |
| R2-2110508 | Service continuity for multicast mode | TD Tech, Chengdu TD Tech |
| R2-2110599 | Inter-cell mobility for MBS | Huawei, HiSilicon |
| R2-2110603 | Reply on MBS outstanding issues in SA WG2 | Huawei, HiSilicon |
| R2-2110653 | Multicast Service Continuity | ZTE, Sanechips |
| R2-2110676 | Remaining PDCP issues for MBS | Xiaomi Communications |
| R2-2110742 | Multicast service continuity in mobility and PTM/PTP switching | Intel Corporation |
| R2-2110890 | Lossless PTM/PTP switching | InterDigital |
| R2-2110908 | Discussion on MBS with conditional handover | Futurewei |
| R2-2110955 | Mobility with non-supporting nodes | Nokia, Nokia Shanghai Bell |
| R2-2111048 | Way Forward on PDCP Status Report | CMCC,CBN, QC, Huawei, HiSilicon, CATT, ZTE, OPPO, Xiaomi, Lenovo, Motorola Mobility, TCL, Sharp |
| 8.1.2.2 | Scheduling and power saving | |
| R2-2109517 | Power Saving and Scheduling Aspects for MBS | Samsung |
| R2-2109549 | Remaining issues of scheduling and power saving | MediaTek Inc. |
| R2-2109590 | LCID space for MBS | Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2109626 | MBS MAC layer, scheduling and power saving | Intel Corporation |
| R2-2109684 | LCID related issues for multicast | MediaTek Inc. |
| R2-2109901 | NR Multicast DRX aspects | Qualcomm India Pvt Ltd |
| R2-2109997 | Further Considerations on Group Scheduling for MBS | vivo |
| R2-2110027 | DRX mechanism for MBS PTM reception | Apple |
| R2-2110138 | Discussion on PTM activation-deactivation for MBS | OPPO, CMCC, ZTE, Huawei, HiSilicon, SJTU, NERCDTV, Lenovo, Motorola Mobility, Spreadtrum, TCL, Xiaomi, CATT, MediaTek, Qualcomm, Kyocera, Apple, Sharp, China Unicom, CBN, China Telecom, FGI, APT, InterDigital |
| R2-2110195 | Genaeral aspects for group scheduling | Huawei, HiSilicon |
| R2-2110321 | Further discussion on UP remaining issues | Lenovo, Motorola Mobility |
| R2-2110409 | Aspects on Multicast Inactivity | Ericsson |
| R2-2110492 | Remaining Issues on MBS Group Scheduling | Samsung |
| R2-2110503 | General aspects for NR MBS | TD Tech, Chengdu TD Tech |
| R2-2110509 | Discussion on NR MBS scheduling | TD Tech, Chengdu TD Tech |
| R2-2110515 | Discussion on power saving for NR MBS | Shanghai Jiao Tong University |
| R2-2110654 | L2 identities of NR MBS | ZTE, Sanechips |
| R2-2110655 | DRX for NR Multicast | ZTE, Sanechips |
| R2-2110891 | PTM activation and deactivation | InterDigital |
| R2-2110924 | DL monitoring for MBS DRX | ETRI |
| R2-2111000 | Keeping UE in the same active BWP during multicast session | ASUSTeK |
| R2-2111050 | Discussion on Multicast DRX and LCID Space | CMCC |
| R2-2111115 | Discussion on group scheduling | LG Electronics Inc. |
| R2-2111116 | Discussion on DRX for MBS | LG Electronics Inc. |
| 8.1.2.3 | Other | |
| R2-2109422 | Discussion on Scheduling and Power Saving of MBS | CATT |
| R2-2109468 | Discussion on open issues in MAC running CR | OPPO |
| R2-2109469 | Discussion on Header Compressionfor MBS | OPPO |
| R2-2109683 | Initialization of PDCP state variables | MediaTek Inc. |
| R2-2109706 | Clarification of PTP UM RLC configuration | Fujitsu |
| R2-2109837 | PTM activation and deactivation | InterDigital |
| R2-2109838 | On RLC receiver state variables | InterDigital |
| R2-2109900 | NR MBS user plane aspects | Qualcomm Inc |
| R2-2109994 | PDCP and RLC initialization for MBS reception | vivo |
| R2-2110196 | Window initialization for RLC and PDCP | Huawei, HiSilicon |
| R2-2110197 | PDCP reliability enhancement | Huawei, HiSilicon |
| R2-2110288 | Initialization of PDCP/RLC state variables | TCL Communication Ltd. |
| R2-2110493 | Remaining Issues on Layer-2 Aspects for MBS | Samsung |
| R2-2110656 | Initialization of RLC and PDCP | ZTE, Sanechips |
| R2-2110743 | Remaining issues of MBS user plane | Intel Corporation |
| R2-2110892 | On RLC receiver state variables | InterDigital |
| R2-2111049 | Analysis on PDCP Window Initialization | CMCC |
| R2-2111114 | Discussion on multicast service continuity | LG Electronics Inc. |
| R2-2111117 | Discussion on indication of PTM RLC entity and PTP RLC entity | LG Electronics Inc. |
| 8.1.3 | L3 Centric | |
| R2-2109899 | NR MBS control signaling aspects | Qualcomm Inc |
| R2-2110604 | Report of e-mail discussion: [Post115-e][091][MBS] Remaining control plane issues | Huawei, HiSilicon |
| R2-2111625 | LS on MBS broadcast reception on SCell and non-serving cell | RAN2 |
| 8.1.3.1 | Broadcast Service Continuity | |
| R2-2109423 | Open Issues related to the running 38.304 CR for MBS | CATT, CBN |
| R2-2109424 | Open Issues on MBS interest indication | CATT, CBN |
| R2-2109464 | Discussion on MBS interesting indication for delivery mode 2 | OPPO |
| R2-2109466 | Discussion on MBS service continuity for delivery mode 2 | OPPO |
| R2-2109518 | Service Continuity for Broadcast | Samsung |
| R2-2109998 | Discussion on Broadcast Service Continuity | vivo |
| R2-2110206 | Remaining issues of broadcast service continuity and control plane aspects | Kyocera |
| R2-2110346 | MBS interest indication details | Sony |
| R2-2110377 | MBS service continuity | LG Electronics Inc. |
| R2-2110411 | Open issues in Broadcast Service Continuity | Ericsson |
| R2-2110510 | Service continuity for broadcast mode | TD Tech, Chengdu TD Tech |
| R2-2110552 | Broadcast Service Continuity | Nokia, Nokia Shanghai Bell |
| R2-2110600 | MBS service continuity for delivery mode 2 | Huawei, HiSilicon |
| R2-2110657 | Neighboring cell info for MBS | ZTE, Sanechips |
| R2-2110677 | Security analysis on the MBS interest information | Xiaomi Communications |
| R2-2110744 | Broadcast service continuity | Intel Corporation |
| R2-2111051 | Discussion on MII issues based on SA3 Reply LS | CMCC |
| R2-2111128 | Other L2 centric topics | TD Tech, Chengdu TD Tech |
| R2-2111137 | CQI audit procedure for broadcast mode | Chengdu TD Tech, TD Tech |
| R2-2111264 | MBS service continuity for delivery mode 2 | Huawei, HiSilicon |
| 8.1.3.2 | Notifications | |
| R2-2109425 | Open Issues Related to Multicast Activation Notification | CATT |
| R2-2109467 | Group notification and unicast paging for MBS activation | OPPO |
| R2-2109519 | Notifications for Multicast and Broadcast | Samsung |
| R2-2109999 | Discussion on MBS Notification | vivo |
| R2-2110028 | Access Control for the MBS Service Reception | Apple |
| R2-2110133 | Discussion on multicast activation notification | Spreadtrum Communications |
| R2-2110207 | Open issues of group notifications in NR MBS | Kyocera |
| R2-2110286 | Indication for Multicast Activation notification | TCL Communication Ltd. |
| R2-2110378 | MCCH information acquisition | LG Electronics Inc. |
| R2-2110379 | Remaining issues on group paging | LG Electronics Inc. |
| R2-2110389 | Discussion on MCCH change notification | MediaTek Inc. |
| R2-2110408 | Aspects on Broadcast Notifications | Ericsson |
| R2-2110410 | Aspects on Multicast Notifications | Ericsson |
| R2-2110511 | Discussion on notifications for NR MBS | TD Tech, Chengdu TD Tech |
| R2-2110553 | Multicast notification and RACH | Nokia, Nokia Shanghai Bell |
| R2-2110601 | Notifications for Multicast and Broadcast | Huawei, HiSilicon |
| R2-2110675 | Remaining issues of the multicast notification | Xiaomi Communications |
| R2-2110745 | Multicast Activation Notification and MCCH Change Notification | Intel Corporation |
| R2-2110907 | Clarification on MCCH change notification via DCI | Futurewei |
| R2-2111052 | Remaining Issue on MBS Notification | CMCC |
| 8.1.3.3 | Other | |
| R2-2109426 | Discussion on General RRC Aspects | CATT |
| R2-2109465 | Discussion on beam sweeping transmission for delivery mode 2 | OPPO |
| R2-2109538 | MCCH Contents and RRC Aspects | Samsung |
| R2-2109550 | MCCH Configuration | MediaTek Inc. |
| R2-2109950 | Miscellaneous Aspects of MBS Provisioning | Nokia, Nokia Shanghai Bell |
| R2-2110029 | MBS reception in CONNECTED state | Apple |
| R2-2110322 | Discussion multicast service reception in Scell | Lenovo, Motorola Mobility |
| R2-2110347 | MBS BWP UE capability and MBS resources | Sony |
| R2-2110412 | Other aspects in MBS | Ericsson |
| R2-2110514 | CQI audit procedure for delivery mode 2 | Chengdu TD Tech, TD Tech |
| R2-2110602 | Discussion on RRC parameters for MCCH and MTCH | Huawei, HiSilicon |
| R2-2110658 | PDCP reordering function for Broadcast | ZTE, Sanechips |
| R2-2110674 | Discussion on MBS support on MRDC | Xiaomi Communications |
| R2-2110746 | Miscellaneous MBS L3 open issues | Intel Corporation |
| R2-2111053 | Remaining Issues on RLC/PDCP Configuration in Mode 2 | CMCC |
| R2-2111054 | Support of MBS in CA | CMCC |
| R2-2111134 | Other L3 centric topics | TD Tech, Chengdu TD Tech |
| R2-2111510 | Report of offline discussion: [AT116-e][051][MBS] CP continuation | Huawei, HiSilicon |
| 8.2.1 | Organizational, Requirements and Scope | |
| R2-2109365 | Reply LS on temporary RS for efficient SCell activation in NR CA (R4-2115370; contact: Huawei) | RAN4 |
| R2-2109368 | LS on efficient activation/de-activation mechanism for one SCG R4-2115440; contact: Huawei) | RAN4 |
| R2-2109892 | [Post115-e][215][R17 DCCA] Running 37.340 CR for SCG deactivation | ZTE Corporation, Sanechips |
| R2-2110001 | Inter-MN RRC resume without SN change - RAN2 aspects | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R2-2110427 | Introduction of CPA and inter-SN CPC | CATT |
| R2-2110428 | Introduction of CPA and inter-SN CPC | CATT |
| R2-2110429 | Introduction of CPA and inter-SN CPC | CATT |
| R2-2110504 | Running CR to 38.321 for SCG deactivation | vivo |
| R2-2110866 | [Post115-e][212][R17 DCCA] Running NR/LTE RRCs CR for SCG deactivation (Huawei) | Huawei, HiSilicon |
| R2-2110867 | Introduction of SCG deactivation | Huawei, HiSilicon |
| R2-2110868 | Introduction of SCG deactivation | Huawei, HiSilicon |
| R2-2111453 | Report of email discussion [Post116-e][214][R17 DCCA] UE capabilities (Intel) | Intel Corporation |
| R2-2111635 | [Post115-e][215][R17 DCCA] Running 37.340 CR for SCG deactivation | ZTE Corporation, Sanechips |
| R2-2111638 | Introduction of SCG deactivation | Huawei, HiSilicon |
| R2-2111639 | Introduction of SCG deactivation | Huawei, HiSilicon |
| R2-2111640 | Introduction of CPA and inter-SN CPC | CATT |
| R2-2111641 | Introduction of CPA and inter-SN CPC | CATT |
| R2-2111642 | Introduction of CPA and inter-SN CPC | CATT |
| R2-2111643 | Running CR to 38.321 for SCG activation/deactivation | vivo |
| R2-2111660 | Introduction of CPA and inter-SN CPC | CATT |
| R2-2111661 | Introduction of CPA and inter-SN CPC | CICT |
| 8.2.2.1 | Deactivation of SCG | |
| R2-2109539 | Discussion on SCG deactivation | NTT DOCOMO, INC. |
| R2-2109707 | PDCP re-establishment during SCG deactivation | Fujitsu |
| R2-2109708 | QoS flow remapping during SCG deactivation | Fujitsu |
| R2-2109839 | Deactivation of SCG | InterDigital |
| R2-2109942 | UP issues for SCG deactivation | Samsung |
| R2-2109943 | DC power sharing for deactivated SCG | Samsung |
| R2-2110013 | Deactivation of SCG | Qualcomm Incorporated |
| R2-2110082 | SCG bearer handling for the SCG deactivation | Apple |
| R2-2110212 | Mobility for deactivated SCG | NTT DOCOMO INC. |
| R2-2110296 | Deactivation of SCG | LG Electronics |
| R2-2110323 | Miscellaneous issues on SCG deactivation | Lenovo, Motorola Mobility |
| R2-2110430 | Discussion on Deactivation of SCG | CATT |
| R2-2110516 | Efficient SCG deactivation | Ericsson |
| R2-2110554 | Deactivation of SCG | Nokia, Nokia Shanghai Bell |
| R2-2110870 | UP handling while SCG is deactivated | Huawei, HiSilicon |
| R2-2110871 | Remaining issues on deactivation of SCG | Huawei, HiSilicon |
| R2-2110893 | Deactivation of SCG | InterDigital |
| R2-2111175 | UE assistance information for UE trigered SCG deactivation | Sharp |
| R2-2111176 | reconfigurationwithsync for SCG change with SCG deactivation | Sharp |
| R2-2111249 | UE assistance information for UE trigered SCG deactivation | Sharp |
| R2-2111250 | reconfigurationwithsync for SCG change with SCG deactivation | Sharp |
| R2-2111314 | Summary of [AT116-e][221][R17 DCCA] UP issues for SCG deactivation (Samsung) | Samsung |
| 8.2.2.2 | UE measurements and reporting in deactivated SCG | |
| R2-2109471 | UE measurements and reporting in SCG deactivation | OPPO |
| R2-2109840 | Measurements while the SCG is deactivated | InterDigital |
| R2-2109891 | Discussion on UE behaviour when SCG is deactivated | ZTE Corporation, Sanechips |
| R2-2110000 | UE measurements and reporting in deactivated SCG | Qualcomm Incorporated |
| R2-2110092 | Simple MCG recovery procedure using deactivated SCG for Rel-17 | Apple |
| R2-2110324 | Discussion on RLF and BFD in deactivated SCG | Lenovo, Motorola Mobility |
| R2-2110431 | UE Behavior in Deactivated SCG | CATT |
| R2-2110517 | UE measurements, mobility and suspend/resume in deactivated SCG | Ericsson |
| R2-2110555 | Measurements of deactivated SCG | Nokia, Nokia Shanghai Bell |
| R2-2110660 | Measurements when configured with RACH-less activation | NEC |
| R2-2110872 | UE measurement and reporting while the SCG is deactivated | Huawei, HiSilicon |
| R2-2110894 | Measurements while the SCG is deactivated | InterDigital |
| R2-2111009 | PSCell change while SCG is deactivated | DENSO CORPORATION |
| R2-2111014 | Remaining issues for UE behaviour in deactivated SCG | SHARP Corporation |
| R2-2111017 | UE Measurements in SCG Deactivation | LG Electronics |
| R2-2111094 | UE behavior in deactivated SCG | vivo |
| R2-2111192 | Further discussion on TCI State indication in RRC | MediaTek Inc. |
| 8.2.2.3 | Activation of deactivated SCG | |
| R2-2109470 | Discussion on SCG deactivation for RRC_INACTIVE UE | OPPO |
| R2-2109541 | Discussion on SCG activation | NTT DOCOMO, INC. |
| R2-2109656 | Open issues for activation of deactivated SCG | OPPO |
| R2-2109841 | Activation of SCG | InterDigital |
| R2-2109944 | PHR issues for SCG activation | Samsung |
| R2-2110015 | Activation of deactivated SCG | Qualcomm Incorporated |
| R2-2110090 | Discussion on LS reply for SCG deactivation and MAC CE based SCG deactivation | Apple |
| R2-2110091 | [Draft] LS reply for SCG deactivation | Apple |
| R2-2110122 | Discussion on activation of SCG | Spreadtrum Communications |
| R2-2110325 | Discussion on SCG activation | Lenovo, Motorola Mobility |
| R2-2110432 | Considerations on Activation of Deactivated SCG | CATT |
| R2-2110506 | Activation of a deactivated SCG | vivo |
| R2-2110518 | Efficient activation of deactivated SCG | Ericsson |
| R2-2110661 | UE request for SCG activation | NEC |
| R2-2110869 | [Post115-e][219][R17 DCCA] UE-initiated SCG activation (Huawei) | Huawei, HiSilicon |
| R2-2110873 | Reply LS on efficient activation/de-activation mechanism for one SCG | Huawei, HiSilicon |
| R2-2110895 | Activation of SCG | InterDigital |
| R2-2110909 | Discussion on UE initiated SCG fast activation | Futurewei |
| R2-2111015 | Discussion for bearer handling in deactivated SCG | SHARP Corporation |
| R2-2111018 | Activation of SCG | LG Electronics |
| R2-2111019 | TP for dedicated RACH resource in SCG deactivation | LG Electronics |
| R2-2111077 | Considerations for fast MCG link recovery with deactivated SCG | CMCC |
| R2-2111181 | Discussion on UE initiated SCG activation | SHARP Corporation |
| 8.2.3.1 | CPAC procedures from network perspective | |
| R2-2109658 | Discussion on execution condition of CPAC | NTT DOCOMO INC. |
| R2-2109675 | Discussion on association of execution condition and SN configuration | Intel Corporation |
| R2-2109734 | Discussion on CPAC procedures from NW perspective | vivo |
| R2-2109869 | Network procedures and signalling for CPAC | Ericsson |
| R2-2109871 | Report of e-mail discussion on inter-node message design | Ericsson |
| R2-2109872 | Update of inter-node messages for CPAC | Ericsson |
| R2-2110014 | CPAC procedures and CHO with MR-DC | Qualcomm Incorporated |
| R2-2110326 | Discussion on CPAC from NW perspective | Lenovo, Motorola Mobility |
| R2-2110433 | Discussion on CPAC Procedure from NW Perspective | CATT |
| R2-2110519 | Remaining issues on SN initiated inter-SN CPC | ZTE Corporation, Sanechips |
| R2-2110520 | Further consideration on CPAC procedure | ZTE Corporation, Sanechips |
| R2-2110615 | Resolving open points of Rel-17 CPAC | Nokia, Nokia Shanghai Bell |
| R2-2111085 | CPAC procedure for SCG update | Samsung Electronics |
| R2-2111323 | LS on SN initiated inter-SN CPC | RAN2 |
| R2-2111324 | [AT116-e][223][R17 DCCA] Optional step in SN-initiated inter-SN CPC procedure (Nokia) | Nokia, Nokia Shanghai Bell |
| R2-2111328 | [Draft] LS on SN initiated inter-SN CPC | Ericsson |
| 8.2.3.2 | CPAC procedures from UE perspective | |
| R2-2109735 | Discussion on CPAC procedures from UE perspective | vivo |
| R2-2109870 | UE procedures and signalling for CPAC | Ericsson |
| R2-2109873 | Report of e-mail discussion on support of A3 A5 events for inter-SN CPC | Ericsson |
| R2-2109874 | A3 and A5 events for PSCell | Ericsson |
| R2-2110085 | Discussion on CPAC open issues | Apple |
| R2-2110874 | Remaining issue of CPAC | Huawei, HiSilicon |
| R2-2110935 | Enhancements for CPAC | LG Electronics |
| 8.2.3.3 | Other CPAC aspects | |
| R2-2109762 | Discussion on failure handling for CPAC in NR | China Telecom |
| R2-2109842 | Coexistence of CHO and CPC | InterDigital, Nokia, Nokia Shanghai Bell,ZTE Corporation, Sanechips |
| R2-2110282 | SCG RLF handling in case CPC is configured | ITRI |
| R2-2110327 | Miscellaneous issues on CPAC | Lenovo, Motorola Mobility |
| R2-2110434 | Discussion on CPAC Failure Handling and CPAC Co-existence with CHO | CATT |
| R2-2110521 | Discussion on coexistence of CHO and CPAC | ZTE Corporation, Sanechips |
| R2-2110616 | Final views on CPAC Procedures and Other Functionalities | Nokia, Nokia Shanghai Bell |
| R2-2110662 | CPA with SN-terminated MCG bearer configuration | NEC |
| R2-2110663 | Co-existence of CHO and CPAC | NEC |
| R2-2110896 | Coexistence of CHO and CPC | InterDigital, Nokia, Nokia Shanghai Bell,ZTE Corporation, Sanechips |
| R2-2110998 | Failure handling of Conditional PSCell Addition | DENSO CORPORATION |
| R2-2111078 | Combination of CPAC and CHO | CMCC |
| R2-2111082 | Other CPAC issues | Samsung Electronics |
| R2-2111301 | Summary of Rel-17 eDCCA contributions on CPAC (other aspects) | Interdigital (WI rapporteur) |
| 8.2.4 | Temporary RS for SCell activation | |
| R2-2109472 | Discussion on TRS activation for fast SCell activation | OPPO |
| R2-2109473 | Email report of [Post115-e][218][R17 DCCA] TRS-based SCell activation (OPPO) | OPPO |
| R2-2109657 | Introduction of TRS based SCell activation | OPPO |
| R2-2110505 | Discussion on Temporary RS activation for fast SCell activation | vivo |
| R2-2110556 | Temporary RS activation | Nokia, Nokia Shanghai Bell |
| R2-2110875 | Temporary RS based fast SCell activation | Huawei, HiSilicon |
| R2-2110910 | Discussion on support of Temporary RS for SCell activation | Futurewei |
| R2-2111201 | Discussion on Temporary RS activation for fast SCell activation | vivo |
| R2-2111311 | Summary of [AT116-e][220][R17 DCCA] TRS-based Scell activation details (OPPO) | OPPO |
| R2-2111413 | LS on TRS-based SCell activation details | RAN2 |
| R2-2111592 | WF for TRS activation for fast SCell activation | OPPO |
| 8.2.5 | UE capabilities | |
| R2-2109676 | Report of email discussion [Post115-e][214][R17 DCCA] Capabilities (Intel) | Intel Corporation |
| R2-2109677 | draft 331 CR for DCCA UE capabilities | Intel Corporation |
| R2-2109678 | draft 306 CR for DCCA UE capabilities | Intel Corporation |
| 8.3.1 | Organizational, Requirements and Scope | |
| R2-2109304 | Reply LS on NAS-based busy indication (C1-214917; contact: vivo) | CT1 |
| R2-2109374 | Reply LS on Network Switching for MUSIM (S2-2106673; contact: Qualcomm) | SA2 |
| R2-2110390 | Running NR RRC CR for MUSIM | vivo |
| R2-2110391 | Reply LS on NAS-based busy indication | vivo |
| R2-2110789 | Running CR to 36300 for Multi-USIM devices support | Ericsson |
| R2-2110790 | Running CR to 38300 for Multi-USIM devices support | Ericsson |
| R2-2111096 | Running CR to 36.304 for Multi-USIM devices | China Telecommunications |
| R2-2111179 | Running LTE RRC CR for MUSIM | Samsung Electronics Co., Ltd |
| R2-2111242 | LS reply on UE assistance information for paging collision avoidance (S2-2108144; contact: vivo) | SA2 |
| R2-2111306 | Summary of [AT116-e][241][Slicing] Slice-based cell re-selection algorithm (Ericsson) | Ericsson |
| R2-2111307 | [Draft] LS on RAN2 agreements for MUSIM | vivo |
| R2-2111329 | Reply LS on RAN2 agreements for MUSIM | RAN2 |
| R2-2111438 | Running CR to 36300 for Multi-USIM devices support | Ericsson |
| R2-2111439 | Running CR to 38300 for Multi-USIM devices support | Ericsson |
| R2-2111452 | Running LTE RRC CR for MUSIM | Samsung Electronics Co., Ltd |
| R2-2111566 | Summary of [AT116-e][241][Slicing] Slice-based cell re-selection algorithm (Ericsson) | Ericsson |
| R2-2111602 | Running NR RRC CR for MUSIM | vivo |
| R2-2111632 | Running CR to 36.304 for Multi-USIM devices | China Telecommunications |
| 8.3.2 | Paging collision avoidance | |
| R2-2109407 | Leftover Issues for Paging Collision Avoidance | OPPO |
| R2-2109690 | Remaining Issues on the Paging Collision | ZTE Corporation, Sanechips |
| R2-2109714 | Draft LS on the alternative IMSI | ZTE Corporation, Sanechips |
| R2-2109721 | Definition and solution for paging collision, SI change | Lenovo, Motorola Mobility |
| R2-2109766 | Paging Collision Avoidance Open Issues | Huawei, HiSilicon |
| R2-2109802 | Considerations on Paging Collision Avoidance | Samsung |
| R2-2110190 | Way forward on paging collision | Qualcomm Incorporated |
| R2-2110294 | Discussion on misalignment on EPS paging collision avoidance among SA2, CT1 and RAN2 | China Telecommunications |
| R2-2110392 | Paging collision avoidance | vivo |
| R2-2111020 | Considerations on Paging Collision | LG Electronics |
| R2-2111302 | Summary of agenda 8.3.2: Paging Collision Avoidance (MUSIM) | vivo |
| 8.3.3 | UE notification on network switching for multi-SIM | |
| R2-2109408 | Leftover Issues for Busy Indication | OPPO |
| R2-2109409 | Discussion on Remaining Details for Periodic and Aperiodic Gaps | OPPO |
| R2-2109410 | Discussion on MUSIM Assistance Information for Leaving Case | OPPO |
| R2-2109624 | Remaining issues on network switching | Intel Corporation |
| R2-2109688 | Further Consideration on the Remaining Issues of Scheduling Gap | ZTE Corporation, Sanechips |
| R2-2109689 | Consideration on the Remaining Issues of Switching Procedure | ZTE Corporation, Sanechips |
| R2-2109788 | Further discussion on network switching for MUSIM | Samsung |
| R2-2110048 | Aspects of MUSIM NW Switching and Scheduling Gaps | Apple |
| R2-2110117 | RAN Initiated Paging in MUSIM | Sharp |
| R2-2110118 | RNAU and BUSY indication in MUSIM | Sharp |
| R2-2110129 | Busy indication transmission | Spreadtrum Communications |
| R2-2110142 | Further analysis on switching notification without leaving RRC connection | Nokia, Nokia Shanghai Bells |
| R2-2110143 | On remaining issues for switching notification for leaving RRC connection | Nokia, Nokia Shanghai Bells |
| R2-2110144 | Analysis on signalling procedures and messages for MUSI switching notification | Nokia, Nokia Shanghai Bells |
| R2-2110168 | Further details of MUSIM Gaps | Qualcomm Incorporated |
| R2-2110188 | Remaining issues of network switching for Multi-SIM | Qualcomm Incorporated |
| R2-2110189 | Remaining Issues for MUSIM Network Switching | Charter Communications, Inc |
| R2-2110253 | Open issues on scheduling gap for network switching | NEC |
| R2-2110332 | Switching notification and busy indication | Lenovo, Motorola Mobility |
| R2-2110393 | Discussion on MUSIM Gap Configuration and switching message | vivo |
| R2-2110542 | Disucssion on the remaining issues for NW switching | Huawei, HiSilicon |
| R2-2110775 | Discussion on switchover procedure without leaving RRC_CONNECTED state | Ericsson |
| R2-2110781 | Discussion on switchover procedure for leaving RRC_CONNECTED state | Ericsson |
| R2-2111001 | Interaction between NAS and AS for network switching | ASUSTeK |
| R2-2111021 | Scheduling Gap Handling | LG Electronics |
| R2-2111022 | Paging filtering when AS-based leaving | LG Electronics |
| R2-2111023 | Problems when NAS based Busy Indication | LG Electronics |
| R2-2111103 | Analysis on AS-based solution and NAS-based solution | China Telecommunications |
| R2-2111180 | UE Notification on Network Switching for Multi-SIM | Rakuten Mobile, Inc |
| R2-2111186 | Signalling design on busy indication procedure | DENSO CORPORATION |
| R2-2111197 | Further details on network switching notification | MediaTek Inc. |
| R2-2111222 | Further details on network switching notification | MediaTek Inc. |
| 8.3.4 | Paging with service indication | |
| R2-2109755 | Draft CR to TS36.331 to support paging with service indication for MUSIM | Huawei, HiSilicon |
| R2-2109756 | Draft CR to TS38.331 to support paging with service indication for MUSIM | Huawei, HiSilicon |
| R2-2109761 | Report of [Post115-e][236][MUSIM] Paging with service indication | Huawei, HiSilicon |
| R2-2109767 | Discussion on the paging with service indication | Huawei, HiSilicon |
| R2-2110128 | Supporting of Paging Cause Solution detection | Spreadtrum Communications |
| R2-2110137 | Discussion on the transmission of paging cause | Spreadtrum Communications |
| R2-2110394 | Remaining issues for paging with service indication | vivo |
| R2-2110776 | Introduction of a Paging cause indication | Ericsson |
| R2-2110947 | Discussion on paging service indication for MUSIM | Futurewei Technologies |
| R2-2111171 | Discussion on support of paging cause for MUSIM UE | Samsung Electronics Co., Ltd |
| R2-2111194 | Paging with service indication | MediaTek Inc. |
| R2-2111277 | Draft CR to TS36.331 to support paging with service indication for MUSIM | Huawei, HiSilicon |
| R2-2111278 | Draft CR to TS38.331 to support paging with service indication for MUSIM | Huawei, HiSilicon |
| R2-2111312 | Summary of [232][MUSIM] Paging with serving indication for MUSIM (Huawei) | Huawei |
| R2-2111313 | [Draft] LS on RAN2 agreements for paging with service indication | Huawei |
| R2-2111330 | LS on RAN2 agreements for paging with service indication | RAN2 |
| 8.3.5 | UE capabilities and other aspects | |
| R2-2109625 | UE capabilities for MU-SIM | Intel Corporation |
| R2-2110049 | Aspects of MUSIM UE Capability | Apple |
| R2-2110050 | Additional issues related to MUSIM | Apple |
| R2-2110145 | On MUSIM UE capability and additional switching scenario | Nokia, Nokia Shanghai Bells |
| R2-2110150 | Discussion on UE capability for MUSIM | Samsung |
| R2-2110395 | Multi-USIM related UE capabilities | vivo |
| R2-2110543 | Discussion on UE capability for MUSIM | Huawei, HiSilicon |
| R2-2110788 | UE capabilities for Multi-USIM | Ericsson |
| R2-2111303 | Summary of agenda 8.3.5: UE capabilities (MUSIM) | Ericsson |
| 8.4.1 | Organizational | |
| R2-2109320 | Reply LS on Inter-donor migration (R1-2108529; contact: Huawei) | RAN1 |
| R2-2109350 | LS on BAP- and RRC-related agreements from RAN3#113-e (R3-214476; contact: Ericsson) | RAN3 |
| R2-2109363 | Reply LS on inter-donor migration (R4-2115354; contact: ZTE) | RAN4 |
| R2-2109939 | Updated Rel-17 IAB Workplan | Qualcomm Incorporated, Samsung (WI rapporteurs) |
| R2-2110289 | Running CR to 37.340 for eIAB | vivo |
| R2-2110453 | Running CR to 38.321 on Integrated Access and Backhaul for NR Rel-17 | Samsung Electronics GmbH |
| R2-2111227 | Running CR of TS 38.340 for eIAB updated based on approach A | Huawei, HiSilicon |
| R2-2111228 | Running CR of TS 38.340 for eIAB updated based on approach B | Huawei, HiSilicon |
| R2-2111450 | Running CR to 38.300 for eIAB | Qualcomm |
| R2-2111451 | Running CR to 37.340 for eIAB | vivo |
| R2-2111604 | Running CR to 38.331 on NR IAB enhancements | Ericsson |
| R2-2111637 | Running CR of TS 38.340 for eIAB | Huawei, HiSilicon |
| 8.4.2 | Enhancements to improve topology-wide fairness multi-hop latency and congestion mitigation | |
| R2-2109582 | Long BSR Format with Extended LCG | CATT |
| R2-2109611 | Discussion on remaining open issues of LCG range extension and congestion | Intel Corporation |
| R2-2109748 | BSR format and reporting in IAB | Fujitsu |
| R2-2109782 | LCG extension for eIAB | Huawei, HiSilicon |
| R2-2109843 | On BSR formats for IAB | InterDigital |
| R2-2109844 | UL Congestion mitigation in multi-hop IAB | InterDigital |
| R2-2109854 | Discussion on LCG extension and UL hop-by-hop flow control feedback | ZTE, Sanechips |
| R2-2110290 | Discussion on LCG extension issues | vivo |
| R2-2110306 | Discussion on LCG extension and congestion migitation for IAB | Lenovo, Motorola Mobility |
| R2-2110422 | Finalizing enhancements to LCG space and BSR triggering including pre-emptive BSR | Samsung Electronics GmbH |
| R2-2110806 | Uplink hop-by-hop flow control | Nokia, Nokia Shanghai Bell |
| R2-2110807 | BSR formats for LCG extension | Nokia, Nokia Shanghai Bell |
| R2-2110883 | On Topology-wide Fairness, Multi-hop Latency, and Congestion in IAB Network | Ericsson |
| R2-2110897 | On BSR formats for IAB | InterDigital |
| R2-2110898 | UL Congestion mitigation in multi-hop IAB | InterDigital |
| R2-2110911 | Enhancements to Rel. 17 IAB RLF indications and local routing | Futurewei Technologies |
| R2-2111155 | Stage-3 details of LCG extension | LG Electronics Inc. |
| R2-2111174 | Remaining issues -Fairness, latency, congestion | Rakuten Mobile, Inc |
| R2-2111520 | Summary of discussion [AT116-e][031][eIAB] MAC - LCG extension and BSR (Samsung) | Samsung |
| 8.4.3 | Topology adaptation enhancements | |
| R2-2109583 | Reduction of Service Interruption during Intra-donor IAB Migration | CATT |
| R2-2109584 | Discussion on Type-2/3 RLF indication | CATT |
| R2-2109585 | Discussion on left issues of local routing and routing | CATT |
| R2-2109612 | IAB dual connection, RLF and local rerouting | Intel Corporation |
| R2-2109613 | Intra-donor CU service interruption reduction | Intel Corporation |
| R2-2109614 | Inter-donor CU topology migration, topology redundancy and CP-UP separation | Intel Corporation |
| R2-2109749 | Open issues on (re-)routing | Fujitsu |
| R2-2109750 | Open issues on Type-2 BH RLF indication | Fujitsu |
| R2-2109751 | UE handover during inter-donor-CU migration | Fujitsu |
| R2-2109775 | Discussion on the inter-CU routing | Samsung |
| R2-2109783 | Summary of [Post115-e][088][eIAB] inter-CU routing open issues | Huawei, HiSilicon |
| R2-2109784 | Leftover proposals in Summary of [Post114-e][075][eIAB] Open Issues on Re-routing | Huawei, HiSilicon |
| R2-2109785 | RLF indication for R17-IAB | Huawei, HiSilicon |
| R2-2109786 | F1 over NR access link and CHO | Huawei, HiSilicon |
| R2-2109845 | CHO in IAB | InterDigital |
| R2-2109846 | DAPS support in IAB | InterDigital |
| R2-2109855 | Discussion on inter-donor topology redundancy | ZTE, Sanechips |
| R2-2109856 | Discussion on RLF indication and local re-routing | ZTE, Sanechips |
| R2-2109861 | Discussion on inter-donor migration and service interruption reduction | ZTE, Sanechips |
| R2-2109940 | BAP processing at the boundary node: Modelling A and B | Qualcomm Incorporated |
| R2-2109941 | Enhancements to RLF indications in IAB | Qualcomm Incorporated |
| R2-2110203 | Routing and re-routing enhancements for eIAB | Kyocera |
| R2-2110204 | Details of BH RLF Indications for eIAB | Kyocera |
| R2-2110291 | Discussion on issues of local re-routing based on congestion | vivo |
| R2-2110292 | Miscellaneous Issues of Topology Adaptation | vivo |
| R2-2110293 | Miscellaneous issues on CP-UP separation | vivo |
| R2-2110307 | Discussion on local rerouting and local bearer remapping for IAB | Lenovo, Motorola Mobility |
| R2-2110343 | Rel-17 BAP Operations | CANON Research Centre France |
| R2-2110344 | Discussion on RLF indication enhancements | CANON Research Centre France |
| R2-2110348 | Introduce cost factor in local re-routing | Sony |
| R2-2110418 | Triggers for local rerouting | Samsung Electronics GmbH |
| R2-2110723 | IAB inter-CU (re)routing | Nokia, Nokia Shanghai Bell |
| R2-2110724 | Re-routing ehnancements and RLF indications in IAB | Nokia, Nokia Shanghai Bell |
| R2-2110885 | Boundary IAB node behaviour for partial inter-donor migration | Ericsson |
| R2-2110886 | On Local Routing and Type 2/3 RLF Handling | Ericsson |
| R2-2110888 | Remaining Issues Related to CP/UP Separation in IAB Network | Ericsson |
| R2-2110899 | CHO in IAB | InterDigital |
| R2-2110900 | DAPS support in IAB | InterDigital |
| R2-2111057 | Open issues for type-2/3 RLF indication | ETRI |
| R2-2111088 | CP-UP separation and other topology adaptation issues | Samsung Electronics |
| R2-2111142 | Resolving open issues on BH RLF indications | LG Electronics |
| R2-2111156 | Further discussion on enhancement of local re-routing | LG Electronics Inc. |
| R2-2111157 | Remaining issues on enhancements of topology adaptation and congestion mitigation | LG Electronics Inc. |
| R2-2111203 | Analysis of some remaining issues for inter-donor & inter-topology routing | Futurewei Technologies |
| R2-2111266 | Summary of [Post115-e][088][eIAB] inter-CU routing open issues | Huawei, HiSilicon |
| R2-2111500 | Summary of [AT116-e][047][eIAB] Routing and re-routing continued | Huawei, HiSilicon |
| R2-2111501 | Summary of [AT116-e][033][eIAB] CP-UP separation (vivo) | vivo |
| R2-2111532 | [AT116-e][032][eIAB] RLF indications | LGE (Rapporteur) |
| R2-2111539 | [AT116-e][032][eIAB] RLF indications | LGE (Rapporteur) |
| R2-2111595 | Summary of [AT116-e][047][eIAB] Routing and re-routing continued | Huawei, HiSilicon |
| 8.5.1 | Organizational | |
| R2-2109327 | LS on TA-based propagation delay compensation (R1-2108635; contact: Huawei) | RAN1 |
| R2-2110441 | Stage-2 Running CR for Rel-17 IIoT/URLLC | Nokia, Nokia Shanghai Bell |
| R2-2110495 | MAC Running CR for Rel-17 IIoT/URLLC | Samsung |
| R2-2111217 | LS on propagation delay compensation (R1-2110647; contact: Huawei) | RAN1 |
| 8.5.2 | Enhancements for support of time synchronization | |
| R2-2109302 | RE: LS on Time Synchronization | IEEE 1588 WG |
| R2-2109599 | Discussion about propagation delay compensation for accurate time synchronization | Huawei, HiSilicon |
| R2-2109776 | Summary of PDC Issues | Ericsson |
| R2-2109925 | Propagation Delay Compensation for TSN | Qualcomm Incorporated |
| R2-2109990 | Discussion on propagation delay compensation | vivo |
| R2-2110107 | Remaining FFSs on time synchronization and PDC | ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
| R2-2110199 | Discussion on propagation delay compensation for TSN | NTT DOCOMO INC. |
| R2-2110318 | Left issues for propagation delay compensation | Lenovo, Motorola Mobility |
| R2-2110442 | Views on Support of Propagation Delay Compensation | Nokia, Nokia Shanghai Bell |
| R2-2110496 | Issues on Propagation Delay Compensation | Samsung |
| R2-2110587 | Consideration on the support of time synchronization enhancement | OPPO |
| R2-2110801 | Remaining issues of timing synchronization | Intel Corporation |
| R2-2110963 | Discussion about propagation delay compensation enhancements | China Telecommunications |
| R2-2111046 | Time synchronization for TSN based on RAN1 progress | CMCC |
| R2-2111257 | Summary of AI 8.5.2 on Time Synchronization | CMCC |
| R2-2111282 | Report of [AT116-e][502][IIOT] Time Synchronization | CMCC |
| 8.5.3 | Uplink enhancements for URLLC in unlicensed controlled environments | |
| R2-2109600 | Remaining issues about uplink enhancements for URLLC in UCE | Huawei, HiSilicon |
| R2-2109653 | cg-RetransmissionTimer configured without autonomousTx | CATT |
| R2-2109777 | Harmonizing UL CG enhancements in NR-U and URLLC | Ericsson |
| R2-2109926 | CG Harmonization for Unlicensed Controlled Environment | Qualcomm Incorporated |
| R2-2109991 | Remaining Issue about Autonomous Re-transmission | vivo |
| R2-2110243 | Remaining details on enhancements for URLLC in UCE | Lenovo, Motorola Mobility |
| R2-2110443 | Remaining Issues on HARQ Process Selection for Configured Grant | Nokia, Nokia Shanghai Bell |
| R2-2110497 | Remaining Issues on Intra-CG Prioritization and LCH-based Prioritization in UCE | Samsung |
| R2-2110588 | Consideration on URLLC over NR-U | OPPO |
| R2-2110623 | Further Consideration on the Intra-UE multiplexing in UCE | ZTE Corporation,Sanechips |
| R2-2110672 | Remaining issues of CG harmonization | Xiaomi Communications |
| R2-2110754 | Remaining issues for UCE | MediaTek Inc. |
| R2-2110916 | IIoT operation in unlicensed controlled environments | InterDigital |
| R2-2111104 | Remaining issues of IIoT in UCE | III |
| R2-2111169 | Remaining issues in intraCG-Prioritization | LG Electronics Inc. |
| R2-2111262 | Summary of Agenda Item 8.5.3: Uplink enhancements for URLLC in unlicensed controlled environments | OPPO |
| R2-2111281 | Report of [AT116-e][501][IIOT] Open issues for UCE | OPPO |
| R2-2111508 | Report of [AT116-e][501][IIOT] Open issues for UCE | OPPO |
| 8.5.4 | RAN enhancements based on new QoS | |
| R2-2109601 | Discussion on two-level PERs for survival time handling | Huawei, HiSilicon |
| R2-2109602 | Summary of [Post115-e][513][IIoT] QoS survival time | Huawei, HiSilicon |
| R2-2109603 | TP of baseline CR for Survival Time state operation | Huawei, HiSilicon |
| R2-2109654 | HARQ NACK solution: addressing concerns and design details | CATT, CMCC |
| R2-2109655 | TPs capturing HARQ-NACK solution | CATT |
| R2-2109709 | L1/L2 configuration adaptation | Fujitsu |
| R2-2109710 | Additional thought on supporting N>1 | Fujitsu |
| R2-2109778 | RAN enhancements based on new QoS related parameters | Ericsson |
| R2-2109927 | RAN Enhancement to support Survival Time | Qualcomm Incorporated |
| R2-2109992 | Discussion on HARQ NACK solution | vivo |
| R2-2110067 | Remaining QoS solution aspects | Apple |
| R2-2110068 | Adaptive configuration for CG/SPS | Apple |
| R2-2110069 | Further considerations on survival time for new QoS | Apple |
| R2-2110108 | N and combined Tx-side timer for IIoT QoS | ZTE, Sanechips, China Southern Power Grid Co., Ltd, TCL Communication Ltd., vivo |
| R2-2110201 | Discussion on survival time state | NTT DOCOMO INC. |
| R2-2110227 | Remaining issues on the support of survival time | Lenovo, Motorola Mobility |
| R2-2110263 | Discussion on the RAN solution for introduction of new QoS parameters | CMCC |
| R2-2110345 | Finalising Survival Time related enhancements | Samsung Electronics GmbH |
| R2-2110444 | An Overview of Survival Time Enhancements | Nokia, Nokia Shanghai Bell |
| R2-2110589 | Consideration on the support of survival time | OPPO |
| R2-2110673 | Clarification on the survival time requirement | Xiaomi Communications |
| R2-2110791 | On counting HARQ-NACKs for triggering survival time state | Futurewei Technologies |
| R2-2110802 | Survival time handling | Intel Corporation |
| R2-2110913 | Enhancements based on new QoS requirements | InterDigital |
| R2-2110918 | Issues with UE Survival Time support | Sequans Communications |
| R2-2110965 | Discussion on RAN enhancement to support survival time | China Telecommunications |
| R2-2111167 | Remaining aspects in ST mechanism | LG Electronics Inc. |
| R2-2111183 | Discussion of RAN Enhancements to Support Survival Time | TCL Communication Ltd. |
| 8.6.1 | Organizational | |
| R2-2109308 | Reply LS on Small data transmission (C1-215152; contact: Apple) | CT1 |
| R2-2109321 | Reply LS on on physical layer aspects of small data transmission (R1-2108533; contact: vivo) | RAN1 |
| R2-2109330 | LS on the TA validation and mapping details for CG-SDT (R1-2108649; contact: ZTE) | RAN1 |
| R2-2110185 | Running MAC CR for small data | Huawei, HiSilicon |
| R2-2110186 | Remaining issue for MAC spec | Huawei, HiSilicon |
| R2-2110187 | Summary of [Post115-e][507][SDT] MAC running CR update (Huawei) | Huawei, HiSilicon |
| R2-2110573 | RRC Running CR for SDT | ZTE Corporation (rapporteur) |
| R2-2110576 | [DRAFT] Reply LS on the physical layer aspects of small data transmission | ZTE Corporation, Sanechips |
| R2-2110808 | Stage-2 running CR Introduction of SDT | Nokia, Nokia Shanghai Bell |
| R2-2111219 | Reply LS on the physical layer aspects of small data transmission (R1-2110661; contact: ZTE) | RAN1 |
| R2-2111446 | LS on the ROHC continuity for SDT | RAN2 |
| R2-2111611 | Reply LS on the physical layer aspects of small data transmission | RAN2 |
| 8.6.2 | User plane common aspects | |
| R2-2109437 | Further Discussion on User Plane Aspect of Small Data Transmission | vivo |
| R2-2109524 | User Plane Common Aspects of RACH and CG based SDT | Samsung Electronics Co., Ltd |
| R2-2109593 | Common aspects for SDT | Ericsson |
| R2-2109621 | User plane leftover issues for SDT procedure | Intel Corporation |
| R2-2109711 | Remaining UP open issues | Fujitsu |
| R2-2109768 | Discussion on user plane issues of SDT | OPPO |
| R2-2110030 | User plane aspects of SDT | Apple |
| R2-2110182 | User plane common aspects for SDT | Huawei, HiSilicon |
| R2-2110255 | Remaining user plane aspects of SDT | NEC |
| R2-2110328 | The UP common issues for small data transmissions | Lenovo, Motorola Mobility |
| R2-2110397 | Consideration on UP remaining issues of SDT? | CATT |
| R2-2110575 | User plane common aspects for SDT | ZTE Corporation, Sanechips |
| R2-2110667 | Clarification on the data volume computation | Xiaomi Communications |
| R2-2110669 | RACH failure in subsequent data transmission phase | Xiaomi Communications |
| R2-2110752 | Remaining issues on UP aspects of SDT | Qualcomm Incorporated |
| R2-2110809 | UP aspects for SDT | Nokia, Nokia Shanghai Bell |
| R2-2110915 | User plane aspects of small data transmission | InterDigital |
| R2-2110983 | Handling of legacy TAT and CG-SDT-TAT | LG Electronics Inc. |
| R2-2111039 | Leftover UP common issues of SDT | CMCC |
| R2-2111124 | Remaining UP issues in SDT | LG Electronics Inc. |
| R2-2111519 | [AT116-e][503][SData] Summary of UP SDT open issues | LG Electronics Inc. (Rapporteur) |
| 8.6.3 | Control plane common aspects | |
| R2-2109438 | Handling of non-SDT Data Arrival via BSR | vivo |
| R2-2109439 | Discussion on RRC-controlled Small Data Transmission | vivo |
| R2-2109525 | Control Plane Aspects of SDT Procedure | Samsung Electronics Co., Ltd |
| R2-2109526 | Handling legacy control plane operations during SDT procedure | Samsung Electronics Co., Ltd |
| R2-2109594 | SDT Faliure Handling | Ericsson |
| R2-2109595 | CP aspects for SDT | Ericsson |
| R2-2109617 | DCCH-based indication of non-SDT data arrival | Intel Corporation, ZTE corporation, Sanechips, Samsung, CMCC, Qualcomm, OPPO, Sharp, Xiaomi, Sony, CATT, FGI, Asia Pacific Telecom, Radisys |
| R2-2109618 | Draft CR for introduction of DCCH solution for non-SDT data arrival | ZTE corporation, Sanechips, Intel Corporation, Samsung, CMCC, Qualcomm, OPPO, Sharp, Xiaomi, Sony, CATT, FGI, Asia Pacific Telecom, Radisys |
| R2-2109619 | DCCH vs CCCH based approach for indication of non-SDT data arrival | Intel Corporation, ZTE corporation, Sanechips, Samsung, Qualcomm, OPPO, Sharp, Xiaomi, Sony, CATT, Apple |
| R2-2109620 | Control plane leftover issues for SDT procedure | Intel Corporation |
| R2-2109712 | Handling of SDTF detection timer | Fujitsu |
| R2-2109713 | RAN paging reception and response during SDT | Fujitsu |
| R2-2109769 | Discussion on control plane issues of SDT | OPPO |
| R2-2110031 | Control plane aspects of SDT | Apple |
| R2-2110032 | SDT specific NAS and AS interaction | Apple |
| R2-2110033 | Power Saving for SDT | Apple |
| R2-2110184 | Discussion on the NAS aspects of Small Data | Huawei, HiSilicon |
| R2-2110209 | Remaining Issues on the Arrival of Non-SDT Traffic | FGI, Asia Pacific Telecom |
| R2-2110254 | Remaining control plane aspects of SDT | NEC |
| R2-2110329 | Discussion on CP data transmission over SDT | Lenovo, Motorola Mobility |
| R2-2110398 | Consideration on NAS and AS Interaction | CATT |
| R2-2110399 | Consideration on CP issues | CATT |
| R2-2110572 | Control plane common aspects of SDT | ZTE Corporation, Sanechips |
| R2-2110595 | Control plane common aspects for SDT | Huawei, HiSilicon |
| R2-2110596 | Non-SDT data arrival | Huawei, HiSilicon, InterDigital, LGE, Ericsson, ASUSTeK, Nokia, Nokia Shanghai Bell, Google, Rakuten Mobile, Fujitsu, NEC |
| R2-2110668 | Paging reception during SDT | Xiaomi Communications |
| R2-2110753 | Remaining issues on CP aspects of SDT | Qualcomm Incorporated |
| R2-2110797 | Draft LS to CT1 on small data transmission | Apple |
| R2-2110818 | SDT control plane aspects | Nokia, Nokia Shanghai Bell |
| R2-2110819 | RRC procedure for SDT | Nokia, Nokia Shanghai Bell |
| R2-2110865 | Untreated proposal from [Post113-e][503] | InterDigital |
| R2-2111275 | Comments on the proposed CCCH solution for non-SDT data arrival | Intel Corporation, ZTE corporation, Apple |
| R2-2111509 | Further clarifications on non-SDT arrival solutions | Huawei, HiSilicon, InterDigital, LGE, Ericsson, ASUSTeK, Nokia, Nokia Shanghai Bell, Google, NEC, Fujitsu, Rakuten Mobile |
| R2-2111523 | Comments to R2-2111509 for non-SDT data arrival | Intel Corporation, ZTE corporation, Sanechips, Samsung, Xiaomi, Qualcomm, Apple, Radisys |
| 8.6.4 | Aspects specific to RACH based schemes | |
| R2-2109440 | Supporting subsequent UL transmission during RA-SDT | vivo |
| R2-2109527 | RACH configuration for Small Data Transmission. | Samsung Electronics Co., Ltd |
| R2-2109591 | RACH based small data transmission | Ericsson |
| R2-2109622 | RA-SDT leftover issues | Intel Corporation |
| R2-2109770 | Discussion on swiching from RA-SDT to legacy RACH | OPPO |
| R2-2110123 | Discussion on RACH-based SDT | Spreadtrum Communications |
| R2-2110208 | C-RNTI handling for SDT | FGI, Asia Pacific Telecom |
| R2-2110210 | Issues of the Subsequent Data Transmission | FGI, Asia Pacific Telecom |
| R2-2110330 | Analysis on open issues of RA based SDT | Lenovo, Motorola Mobility |
| R2-2110349 | Remaining issues of RACH-based SDT in NR | Sony |
| R2-2110400 | Anchor relocation during SDT | CATT |
| R2-2110594 | Small data transmission with RA-based schemes | Huawei, HiSilicon |
| R2-2110624 | Discussion on RA-based small data transmission | Google Inc. |
| R2-2110760 | Remaining issues on RACH based SDT | Qualcomm Incorporated |
| R2-2110810 | RA specific aspects for SDT | Nokia, Nokia Shanghai Bell |
| R2-2110984 | Switching cases of SDT and non-SDT | LG Electronics Inc. |
| R2-2111002 | Discussion on fallback to legacy RA for RA-SDT | ASUSTeK |
| R2-2111038 | Discussion on RACH based SDT | CMCC |
| 8.6.5 | Aspects specific to CG based schemes | |
| R2-2109441 | Supporting Small Data Transmission via CG PUSCH | vivo |
| R2-2109528 | TAT-SDT expiry handing during the CG-SDT procedure | Samsung Electronics Co., Ltd |
| R2-2109592 | Details of CG based SDT | Ericsson |
| R2-2109623 | CG-SDT leftover issues | Intel Corporation |
| R2-2109645 | Discussion on left issue for CG-SDT resource release | SHARP Corporation |
| R2-2109771 | Discussion on the procedure of CG-SDT | OPPO |
| R2-2109772 | Discussion on handling of CG-SDT resources | OPPO |
| R2-2110034 | CG specific SDT procedure | Apple |
| R2-2110183 | CG-based schemes for SDT | Huawei, HiSilicon |
| R2-2110245 | Further details on CG based small data transmission | Lenovo, Motorola Mobility |
| R2-2110248 | Additional aspects of CG based SDT | Ericsson |
| R2-2110401 | Remaining issues for CG-SDT | CATT |
| R2-2110574 | Open issues for CG based SDT | ZTE Corporation, Sanechips |
| R2-2110625 | Discussion on CG-based small data transmission | Google Inc. |
| R2-2110670 | Summary of [Post115-e][509][SDT] CG open issues (Xiaomi) | Xiaomi Communications |
| R2-2110671 | Remaining issues of CG SDT in RAN2 | Xiaomi Communications |
| R2-2110761 | Remaining issues on CG based SDT | Qualcomm Incorporated |
| R2-2110764 | CG-SDT Switch to RA during subsequent transmissions | NEC Telecom MODUS Ltd. |
| R2-2110914 | CG-based SDT selection and configuration | InterDigital |
| R2-2110961 | Discussion on open issues for CG based SDT | China Telecommunications |
| R2-2110986 | Remaining CG-SDT issues in SDT | LG Electronics Inc. |
| R2-2111031 | Aspects specific to CG-SDT | Nokia, Nokia Shanghai Bell |
| R2-2111125 | Autonomous retransmission in CG-SDT | LG Electronics Inc. |
| R2-2111185 | Discussion on CG based Small Data Transmission | TCL Communication Ltd. |
| R2-2111199 | Open issues for CG based SDT | ZTE Corporation, Sanechips |
| 8.7.1 | Organizational | |
| R2-2109303 | Reply LS on establishment/resume cause value and UAC on L2 SL Relay (C1-214795; contact: OPPO) | CT1 |
| R2-2109399 | Work planning for R17 SL relay | OPPO, CMCC |
| R2-2109400 | Running CR for TS 38.351 | OPPO |
| R2-2109401 | Remaining Open issue list of R17 Sidelink Relay WI | OPPO |
| R2-2109543 | Stage 2 Running CR on Introduction of R17 SL Relay | MediaTek Inc. |
| R2-2110054 | MAC running CR for SL relay | Apple (rapporteur) |
| R2-2110447 | Running CR of 38.323 for SL Relay | Samsung |
| R2-2110490 | RRC running CR for SL relay | Huawei, HiSilicon |
| R2-2110687 | Running CR of 38.304 for SL relay | Ericsson |
| R2-2111123 | Discussion on LS on discovery and relay (re)selection | OPPO |
| R2-2111236 | Reply LS on discovery and relay (re)selection (S2-2107972; contact: CATT) | SA2 |
| R2-2111253 | Discussion on LS on discovery and relay (re)selection | CATT |
| R2-2111370 | [draft] Reply LS on discovery and relay (re)selection | CATT |
| R2-2111371 | Summary [AT116-e][620][Relay] Reply LS to SA2 on discovery and relay (re)selection (CATT) | CATT |
| R2-2111372 | Summary of [621] | OPPO |
| R2-2111437 | Stage 2 Running CR on Introduction of R17 SL Relay | MediaTek Inc. |
| R2-2111445 | Running CR of 38.323 for SL Relay | Samsung |
| R2-2111449 | Running CR of 38.304 for SL relay | Ericsson |
| R2-2111485 | Sidelink Relay Adaptation Protocol (SRAP) Specification | OPPO |
| R2-2111487 | Reply LS on discovery and relay (re)selection | CATT |
| R2-2111489 | Sidelink Relay Adaptation Protocol (SRAP) Specification | OPPO |
| R2-2111490 | Introduction of Rel-17 Sidelink Relay | Huawei, HiSilicon |
| R2-2111583 | Reply LS on discovery and relay (re)selection | RAN2 |
| R2-2111644 | 38.321 CR to introduce Sidelink Relay | Apple (Rapporteur) |
| 8.7.2.1 | Control plane procedures | |
| R2-2109414 | Discussion on Control Plane Aspects for L2 Relay | OPPO |
| R2-2109419 | Remaining issues on paging and SIB forwarding in L2 U2N relay | Qualcomm Incorporated |
| R2-2109427 | Remaining issues on RRC connection management of L2 U2N relay | Qualcomm Incorporated |
| R2-2109507 | Control Plane Procedures of L2 Relay | CATT |
| R2-2109508 | Discussion on Remote UE's Paging via Dedicated RRC Message | CATT |
| R2-2109544 | Discussion on SI Modification and PWS Notification | MediaTek Inc. |
| R2-2109545 | Remaining issue for RLF handling | MediaTek Inc. |
| R2-2109556 | Discussion on RRC connection management for L2 sidelink relay | Huawei, HiSilicon |
| R2-2109557 | SI forwarding and paging for L2 sidelink relay | Huawei, HiSilicon |
| R2-2109644 | Discussion on left issue for paging delivery | SHARP Corporation |
| R2-2109696 | SI forwarding | NEC Corporation |
| R2-2109729 | Monitoring Paging by a U2N Relay | Lenovo, Motorola Mobility |
| R2-2109763 | Discussion on system information delivery open issues | China Telecom |
| R2-2109811 | SIB handling in sidelink L2 U2N relay | Nokia, Nokia Shanghai Bell |
| R2-2109859 | Consideration on the connection management of SL relay | ZTE, Sanechips |
| R2-2109860 | Consideration on the system information acquisition and paging in SL relay | ZTE, Sanechips |
| R2-2109928 | Summary of [POST115-e][610][Relay] Control Plane Procedures (InterDigital) | InterDigital |
| R2-2109929 | Open Issues on Paging Procedure for L2 UE to NW Relays | InterDigital |
| R2-2109930 | Open Issues on SI for L2 UE to NW Relays | InterDigital |
| R2-2109934 | Connection Establishment Procedure for L2 UE to NW Relays | InterDigital |
| R2-2109959 | Remaining issues of system information forwarding for L2 U2N Remote UE | Intel Corporation |
| R2-2109964 | Access control support for L2 U2N Relay | Intel Corporation |
| R2-2110064 | Remaining issues on SIB forwarding | Apple |
| R2-2110065 | RNA Update via L2 UE-to-NW Relay | Apple |
| R2-2110121 | Discussion on control plane procedures for L2 U2N relay | Spreadtrum Communications |
| R2-2110163 | Control plane procedure - SIB delivery, and timer for remote UE | LG Electronics France |
| R2-2110165 | L2 relay control plane issues | Kyocera |
| R2-2110213 | Open issues on L2 Control Plane Procedures | vivo |
| R2-2110215 | Draft LS on L2 U2N relay issues | vivo |
| R2-2110221 | Discussion on SI and short message delivery | Xiaomi |
| R2-2110222 | Discussion on connection control | Xiaomi |
| R2-2110284 | Discussion on access control of L2 relay | SHARP Corporation |
| R2-2110303 | Considerations on control plane issues | Lenovo, Motorola Mobility |
| R2-2110350 | Area specific SI issue in L2 relay | Sony |
| R2-2110363 | Discussion on establishment cause of relay UE | Xiaomi, Apple, Lenovo, Motorola Mobility |
| R2-2110448 | Connection management and PC5/Uu RLC configurations | Samsung |
| R2-2110449 | Remaining issues for SI message forwarding | Samsung |
| R2-2110450 | Remaining issues for paging delivery | Samsung |
| R2-2110470 | Issue with Forwarding SIB9 to remote UE | Nokia, Nokia Shanghai Bell |
| R2-2110688 | Remaining issues on control plane for L2 sidelink relay | Ericsson |
| R2-2111003 | Discussion on paging procedure and information for U2N Relay | ASUSTeK |
| R2-2111029 | Relayed System Information Acquisition | Futurewei |
| R2-2111190 | SI acquisition, CN Registration and RNAU | Lenovo, Motorola Mobility |
| R2-2111368 | Summary of Agenda item 8.7.2.1: Control plane procedures | Intel Corporation |
| R2-2111373 | Summary of [AT116-e][622][Relay] Remaining proposals from relay control plane (InterDigital) | InterDigital |
| 8.7.2.2 | Service continuity | |
| R2-2109428 | Remaining issues on service continuity of L2 U2N relay | Qualcomm Incorporated |
| R2-2109509 | Service Continuity for L2 U2N Relay | CATT |
| R2-2109546 | Remaining open issues for Service Continuity | MediaTek Inc. |
| R2-2109705 | remaining issues on service continuity | NEC Corporation |
| R2-2109780 | Discussion on remaining issues on service continuity | ZTE Corporation, Sanechips |
| R2-2109933 | Open Issues on Service Continuity for L2 UE to NW Relays | InterDigital |
| R2-2109962 | Service continuity left over issues for L2 U2N relaying | Intel Corporation |
| R2-2110059 | Discussion on U2N Relay UE Identifier | Apple |
| R2-2110060 | [Draft]LS on U2N relay UE identifier | Apple |
| R2-2110066 | Discussion on remaining issues of service continuity | Apple |
| R2-2110164 | Service continuity – depending on relay state | LG Electronics France |
| R2-2110214 | Remaining issues on service continuity in L2 U2N relay | vivo |
| R2-2110220 | Discussion on service continuity | Xiaomi |
| R2-2110302 | Path switching in L2 U2N relay case | Lenovo, Motorola Mobility |
| R2-2110351 | Service continuity open issues in L2 NR sidelink rela | Sony |
| R2-2110371 | Discussion on supported relay UE RRC states in direct to indirect path switch | Nokia, Nokia Shanghai Bell |
| R2-2110488 | Discussion on service continuity for L2 U2N Relay | Huawei, HiSilicon |
| R2-2110499 | Discussion on NR sidelink relay service continuity | OPPO |
| R2-2110689 | Discussion on selecting relay UE in RRC_IDLE or INACTIVE during path switch | Ericsson |
| R2-2110690 | Remaining Issues on service continuity for L2 Sidelink relay | Ericsson |
| R2-2111042 | Service continuity for L2 relay | CMCC |
| R2-2111276 | Summary of Agenda item 8.7.2.2: Service continuity | Huawei, HiSilicon |
| R2-2111365 | Summary of Agenda item 8.7.2.2: Service continuity | Huawei, HiSilicon |
| R2-2111380 | Summary of [AT116-e][626][Relay] Direct-to-indirect path switch (Huawei) | Huawei, HiSilicon |
| 8.7.2.3 | Adaptation layer design | |
| R2-2109398 | Left issues for adaptation layer | OPPO |
| R2-2109429 | Further discussion on adaptation layer of L2 U2N relay | Qualcomm Incorporated |
| R2-2109510 | Adaption Layer Design for L2 U2N Relay | CATT |
| R2-2109547 | Configurations for Bearer Mapping | MediaTek Inc. |
| R2-2109558 | Adaptation layer functionalities for L2 U2N relay | Huawei, HiSilicon |
| R2-2109693 | Remaining issues of Adaptation layer | MediaTek Inc. |
| R2-2109848 | Bearer Mapping Configuration of Adaptation Layer | Futurewei |
| R2-2109862 | Discussion on adaptation layer design | ZTE, Sanechips |
| R2-2109906 | UP aspects on Layer 2 SL relay | Ericsson |
| R2-2109935 | Adaptation Layer Design Remaining Issues | InterDigital |
| R2-2109963 | L2 U2N relaying Adaptation layer design open aspects | Intel Corporation |
| R2-2110216 | Adaptation Layer for Uu and PC5 | vivo |
| R2-2110376 | Finalizing design of Adapt layer | Samsung Electronics GmbH |
| R2-2110385 | On multiplexing of relay UE and remote UE traffic | Samsung Electronics GmbH |
| R2-2110987 | Discussion on Adaptation Layer for L2 U2N Relay | ETRI |
| R2-2111004 | Discussion on bearer mapping on PC5 adaptation layer | ASUSTeK |
| R2-2111041 | Discussion on adaption layer for L2 U2N relay | CMCC |
| R2-2111274 | Summary of 8.7.2.3 Adaptation layer | MediaTek Inc. |
| R2-2111381 | Summary of [AT116-e][627][Relay] Bearer mapping and PC5 PDU format in adaptation layer (MediaTek) | MediaTek Inc. |
| 8.7.2.4 | QoS | |
| R2-2109433 | Remaining issues on E2E QoS enforcement in L2 U2N relay | Qualcomm Incorporated |
| R2-2109511 | QoS Management for L2 Sidelink Relay | CATT |
| R2-2109691 | Views on QoS for sidelink relay | Continental Automotive GmbH |
| R2-2109822 | Considerations on voice and video support for Relays | Philips International B.V., MediaTek, Vivo, FirstNet |
| R2-2109853 | QoS measurement and reporting for path switch procedure | Nokia, Nokia Shanghai Bell |
| R2-2109863 | Discussion on QoS of SL relay | ZTE, Sanechips |
| R2-2109905 | Aspects for QoS management with SL relay | Ericsson |
| R2-2109931 | Discussion on QoS for L2 UE to NW Relays | InterDigital, Philips |
| R2-2110053 | Summary of [Post115-e][604][Relay] Relay QoS (Apple) | Apple |
| R2-2110217 | Left issues on E2E QoS management | vivo |
| R2-2110272 | On recommended bit rate | MediaTek Inc. |
| R2-2110297 | QoS for L2 Sidelink Relay | Fraunhofer IIS, Fraunhofer HHI |
| R2-2110451 | QoS flow control for L2 U2N Relay | Samsung, Philips |
| R2-2110498 | Discussion on QoS for layer 2 relay | OPPO |
| R2-2110562 | Discussion on QoS management of L2 U2N relay | Huawei, HiSilicon |
| R2-2110750 | QoS priority mapping combinations | Beijing Xiaomi Mobile Softwar |
| R2-2111040 | Mechanisms for E2E QoS management | CMCC |
| R2-2111273 | Summary of Agenda item 8.7.2.4: QoS | Qualcomm Incorporated |
| 8.7.3.1 | Discovery | |
| R2-2109430 | Summary report of [Post115-e][611][Relay] Discovery shared and dedicated pool issue (Qualcomm) | Qualcomm Incorporated |
| R2-2109431 | Remaining issues on discovery | Qualcomm Incorporated |
| R2-2109512 | Left Issues for Sidelink Discovery | CATT |
| R2-2109809 | Discussion on SL discovery resource pool configuration | Nokia, Nokia Shanghai Bell |
| R2-2109857 | Further discussion on Relay discovery | ZTE, Sanechips |
| R2-2109903 | Left issues for SL discovery | Ericsson |
| R2-2109932 | Using Shared and Dedicated Resource Pools for Discovery | InterDigital |
| R2-2109960 | Leftover aspects of discovery for L2 U2N relaying | Intel Corporation |
| R2-2110218 | Remaining Issues of Discovery Message Transmission | vivo |
| R2-2110271 | Remaining issues of Relay Discovery | MediaTek Inc. |
| R2-2110304 | Relay Discovery for L2 and L3 relay | Lenovo, Motorola Mobility |
| R2-2110452 | PDCP layer aspects for SL discovery | Samsung |
| R2-2110489 | Remaining issues on relay discovery | Huawei, HiSilicon |
| R2-2110500 | Discussion on common issues for relay and non-relay discovery | OPPO |
| R2-2110501 | Discussion on non-relay discovery | OPPO, Apple, Samsung, Ericsson, Qualcomm |
| R2-2110749 | Discovery Range for 5G ProSe Direct Discovery | Beijing Xiaomi Mobile Software |
| R2-2110751 | Discovery with simultaneous Shared and Dedicated Resource Pools | Beijing Xiaomi Mobile Softwar |
| R2-2111255 | Summary of AI 8.7.3.1 | CATT |
| R2-2111363 | Summary on non-relay discovery | OPPO |
| R2-2111397 | LS on non-relay discovery | RAN2 |
| 8.7.3.2 | Relay re/selection | |
| R2-2109432 | Remaining issues on relay (re)selection | Qualcomm Incorporated |
| R2-2109513 | New Triggers for Relay Reselection | CATT |
| R2-2109823 | U2N Relay UE operation Threshold Conditions: Impact of UE Mobility | Philips International B.V. |
| R2-2109858 | Further discussion on Relay selection | ZTE, Sanechips |
| R2-2109904 | Aspects for SL relay selection and reselection | Ericsson |
| R2-2109961 | Open aspects of L2 U2N Relay (re)selection | Intel Corporation |
| R2-2110166 | Relay reselection upon HO to another gNB | Kyocera |
| R2-2110219 | Remaining issues on Relay (re)selection | vivo |
| R2-2110285 | Discussion on sidelink relay reselection | SHARP Corporation |
| R2-2110305 | Relay (re)selection for L2 and L3 relay | Lenovo, Motorola Mobility |
| R2-2110370 | Uu connection error handling | Nokia, Nokia Shanghai Bell |
| R2-2110502 | Discussion on remaining issue of relay reselection | OPPO |
| R2-2110617 | Discussion on relay reselection aspects | Huawei, HiSilicon |
| R2-2110767 | Support of idle mode mobility for remote-UE in SL UE-to-Nwk relay | Nokia, Nokia Shanghai Bell |
| R2-2111223 | Summary of AI 8.7.3.2 Relay (re)selection | vivo |
| R2-2111382 | Summary of [AT116-e][628][Relay] Signalling from relay UE for cell (re)selection and failure cases (vivo) | vivo |
| 8.8.1 | Organizational | |
| R2-2109349 | Response to LS on Cell reselection with band-specific network slices (R3-214472; contact: ZTE) | RAN3 |
| R2-2109817 | LS on Slice list and priority information for cell reselection (C1-216256; contact: Ericsson) | CT1 |
| R2-2110239 | Running 38.304 CR for RAN slicing | CMCC |
| R2-2110374 | Draft stage 2 CR: Enhancements in RAN slicing | Nokia, Nokia Shanghai Bell |
| R2-2110593 | 38.321 running CR for RAN Slicing | OPPO |
| R2-2110645 | [Post115-e][245][Slicing] Running NR RRC CR for RAN slicing (Huawei) | Huawei |
| R2-2110646 | Running CR of introduction of RAN slicing enhancements for NR | Huawei, HiSilicon |
| R2-2111235 | Reply LS on Slice list and priority information for cell reselection (S2-2107861; contact: CMCC) | SA2 |
| R2-2111400 | Draft stage 2 CR: Enhancements in RAN slicing | Nokia, Nokia Shanghai Bell |
| R2-2111435 | 38.321 running CR for RAN Slicing | OPPO |
| R2-2111443 | Report of [Post116-e][243][Slicing] Running NR RRC CR for RAN slicing (Huawei) | Huawei |
| R2-2111444 | Running NR RRC CR for RAN slicing | Huawei, HiSilicon |
| 8.8.2 | Cell reselection | |
| R2-2109403 | Considerations on slice based cell reselection | Beijing Xiaomi Software Tech |
| R2-2109434 | Remaining issues on slice specific cell reselection | Qualcomm Incorporated |
| R2-2109616 | Further considerations of slice based cell reselection | Intel Corporation |
| R2-2109725 | [Post115-e][244][Slicing] Resolving FFSs for solution 4 (Lenovo) | Lenovo, Motorola Mobility (Rapporteur) |
| R2-2109726 | [draft] LS on Measurement validity for cell reselection based on Network Slicing | Lenovo, Motorola Mobility (Rapporteur) |
| R2-2109727 | Triggers for initiating RAN slicing based cell reselections | Lenovo, Motorola Mobility |
| R2-2109728 | Optimizations for signalling Slice Information | Lenovo, Motorola Mobility |
| R2-2109781 | On optimizing the broadcast of slice support of neighbor cells | Samsung |
| R2-2109787 | Discussion on slice-based cell reselection prioritization | BT plc |
| R2-2110083 | Slice based cell reselection under NW control | Apple |
| R2-2110124 | Discussion on slice based cell reselection | Spreadtrum Communications |
| R2-2110257 | Open issues for slice based cell reselection | CMCC |
| R2-2110274 | A couple of FFS for Cell Reselection | Kyocera |
| R2-2110372 | Slice information provisioning for cell reselection | Nokia, Nokia Shanghai Bell |
| R2-2110437 | Slice based cell reselection | CATT |
| R2-2110522 | Remaining issues on slice priority for cell reselection | Samsung R&D Institute UK |
| R2-2110583 | Discussion on slice based cell reselection | LG Electronics UK |
| R2-2110586 | FFS issues on Solution option 4 | LG Electronics UK |
| R2-2110590 | Consideration on slice-specific cell reselection | OPPO |
| R2-2110647 | Discussion on slice based cell reselection under network control | Huawei, HiSilicon |
| R2-2110698 | Slice support in a serving cell and NAS interaction | Ericsson |
| R2-2110699 | Slice-based cell re-selection algorithm | Ericsson |
| R2-2110901 | Remaining Issues on Slice Info and Option 4 | Samsung R&D Institute UK |
| R2-2110912 | Slice information provided by RRCRelease | Sharp |
| R2-2111010 | Further consideration on slice specific cell reselection | ZTE corporation, Sanechips |
| R2-2111118 | Understanding on the slice list and priority information | ZTE corporation, Sanechips |
| R2-2111268 | [draft] Reply LS on Slice list and priority information for cell reselection | CMCC |
| R2-2111308 | Summary of [AT116-e][240][Slicing] LS reply on slice list and priority information (CMCC) | CMCC |
| R2-2111309 | [Draft] Reply LS on Slice list and priority information for cell reselection | CMCC |
| R2-2111310 | Reply LS on Slice list and priority information for cell reselection | RAN2 |
| 8.8.3 | RACH | |
| R2-2109435 | Remaining issues on slice specific RACH | Qualcomm Incorporated |
| R2-2109747 | Considerations on slice based RACH configuration | Beijing Xiaomi Software Tech |
| R2-2110084 | Slice based RACH configuration | Apple |
| R2-2110258 | Open issues for slice based RACH configuration | CMCC |
| R2-2110373 | Slice grouping considerations | Nokia, Nokia Shanghai Bell |
| R2-2110438 | Analysis on slice based RACH configuration | CATT |
| R2-2110591 | Consideration on slice-specific RACH | OPPO |
| R2-2110648 | Discussion on slice based RACH configuration | Huawei, HiSilicon |
| R2-2110700 | RACH for RAN slicing enhancement | Ericsson |
| R2-2110702 | [Post115-e][242][Slicing] Cell- vs. UE specific slice group signalling (Ericsson) | Ericsson |
| R2-2110712 | Remaining issues for slice-specific RACH configurations | Nokia, Nokia Shanghai Bell |
| R2-2111011 | Further consideration on slice specific RACH | ZTE corporation, Sanechips |
| R2-2111165 | Remaining issues on slice specific RACH prioritization | LG Electronics Inc. |
| 8.8.4 | UE capabilities | |
| R2-2109436 | Consideration on capability of RAN slicing enhancement | Qualcomm Incorporated |
| R2-2109627 | UE capability for Slicing enhancement | Intel Corporation |
| R2-2110259 | Discussion on UE capability for RAN slicing enhancement | CMCC |
| R2-2110592 | Consideration on UE capability for Slicing | OPPO |
| R2-2110649 | Discussion on slice related UE capabilities | Huawei, HiSilicon |
| R2-2111304 | [204] Summary of agenda 8.8.4: UE capabilities (RAN slicing) | Qualcomm Incorporated |
| 8.9.1 | Organizational | |
| R2-2109337 | LS on RAN3 work associated with UE Power Saving (R3-214281; contact: Nokia) | RAN3 |
| R2-2109362 | LS on criteria for RLM/BFD relaxation (R4-2115349; contact: vivo & MediaTek) | RAN4 |
| R2-2110975 | 38.300 running CR for introduction of UE power saving enhancements | Huawei, HiSilicon |
| R2-2111234 | LS Reply on UE Power Saving (S2-2107856; contact: Huawei) | SA2 |
| R2-2111247 | Reply LS on UE Power Saving (R1-2110608; contact: MediaTek) | RAN1 |
| R2-2111491 | 38.300 running CR for introduction of UE power saving enhancements | Huawei, HiSilicon |
| R2-2111657 | 38.331 running CR for introduction of UE power saving enhancements | CATT |
| R2-2111664 | 38.304 Running CR for ePowSav | vivo |
| 8.9.2 | Idle/inactive-mode UE power saving | |
| R2-2109647 | Summary of [Post115-e][089][ePowSav] Paging Subgrouping | Beijing Xiaomi Mobile Softwar |
| R2-2111415 | LS out on paging subgrouping and PEI | RAN2 |
| R2-2111524 | Summary of [AT116-e][045][ePowSav] Paging Subgrouping (Xiaomi) | Xiaomi Communications (email discussion rapporteur) |
| R2-2111525 | LS on UE Power Saving | RAN2 |
| 8.9.2.1 | Architecture | |
| R2-2109490 | Discussion on grouping-based paging | OPPO |
| R2-2109520 | Further details of UE Subgrouping | Samsung Electronics Co., Ltd |
| R2-2109736 | Architecture for paging enhancement by UE subgrouping | vivo |
| R2-2109880 | Further considerations for subgrouping | Intel Corporation |
| R2-2110402 | Further Consideration on Paging Subgrouping | CATT |
| R2-2110413 | CN assigned paging subgroups | Ericsson |
| R2-2110481 | Consideration on Idle/inactive-mode UE power saving | Lenovo, Motorola Mobility |
| R2-2110538 | General scenario consideration on paging subgrouping | Huawei, HiSilicon |
| R2-2110545 | On the co-existence of UE-ID and CN assigned subgroups | Interdigital, Inc. |
| R2-2110546 | UE assistance for CN assigned subgroups | Interdigital, Inc. |
| R2-2110618 | Further Consideration on supporting CN Assigned Subgrouping | ZTE Corporation,Sanechips |
| R2-2110792 | On supporting both CN-assigned subgrouping and UEID-based subgrouping in a same cell | Futurewei Technologies |
| R2-2110967 | UE Paging Subgroup Assignment | MediaTek Inc. |
| R2-2111032 | Remaining details on subgrouping | Nokia, Nokia Shanghai Bell |
| R2-2111073 | Considerations on assistance information and signaling for paging subgrouping | CMCC |
| R2-2111074 | Considerations on UE-ID based subgrouping | CMCC |
| R2-2111535 | Summary of [AT116-e][034][ePowSav] UE assistance for CN subgroups | CMCC |
| 8.9.2.2 | Control and Procedure details | |
| R2-2109453 | PEI configuration and monitoring procedures | Qualcomm Incorporated |
| R2-2109455 | Subgrouping for paging occasions | Qualcomm Incorporated |
| R2-2109491 | Discussion on PEI monitoring | OPPO |
| R2-2109521 | UE Idenity for paging subgrouping | Samsung Electronics Co., Ltd |
| R2-2109522 | DRX cycle for monitoring paging | Samsung Electronics Co., Ltd |
| R2-2109737 | UE subgrouping procedure for paging enhancement | vivo |
| R2-2109779 | Further discussion on CN-assigned paging grouping | Transsion Holdings |
| R2-2110051 | NR UE Power Save Paging Subgrouping aspects | Apple |
| R2-2110352 | Discussion on paging subgroupingenhancements for idle/inactive-mode UE power saving | Sony |
| R2-2110380 | CN assigned subgroup | LG Electronics Inc. |
| R2-2110381 | UE ID based subgroup | LG Electronics Inc. |
| R2-2110415 | PEI monitoring in last used cell | Ericsson, Vodafone |
| R2-2110482 | Considerations on the configuration for UE paging grouping | Lenovo, Motorola Mobility |
| R2-2110539 | Detailed design on paging subgrouping | Huawei, HiSilicon |
| R2-2110547 | Subgroup determination | Interdigital, Inc. |
| R2-2110620 | Consideration on the paging enhancement for idle or inactive UE | ZTE Corporation,Sanechips |
| R2-2110968 | Paging Monitoring with UE Subgrouping | MediaTek Inc. |
| R2-2111033 | UE and NW capabilities on subgrouping | Nokia, Nokia Shanghai Bell |
| R2-2111135 | Remaining issues on PEI monitoring | Beijing Xiaomi Mobile Softwar |
| R2-2111562 | Summary of [AT116-e][046][ePowSav] Paging Early Indication | Ericsson |
| 8.9.3 | Other aspects RAN2 impacts | |
| R2-2109454 | Criteria and configuration for BFD relaxations | Qualcomm Incorporated |
| R2-2109492 | Discussion on signaling aspects of TRS/CSI-RS occasion(s) for idle/inactive Ues | OPPO |
| R2-2109493 | Power saving enhancement for connected mode UE | OPPO |
| R2-2109523 | Other RAN2 aspects of UE Power Saving | Samsung Electronics Co., Ltd |
| R2-2109648 | Discussion on TRS CSI-RS for RRC-IDLE and RRC-INACTIVE State UE | Beijing Xiaomi Mobile Softwar |
| R2-2109738 | Discussion on TRS CSI-RS in idle inactive mode | vivo |
| R2-2109739 | RAN2 impact on RLM/BFD relaxation for power saving | vivo |
| R2-2109878 | Consideration of UE capability for Rel-17 UE power saving | Intel Corporation |
| R2-2109879 | Signalling aspect on criteria of RLM/BFD relaxation | Intel Corporation |
| R2-2110052 | TRS/CSI-RS Signaling Aspects for IDLE/INACTIVE UEs | Apple |
| R2-2110194 | Discussion on RLM_BFD measurement relaxation | Xiaomi Communications |
| R2-2110335 | TRS/CSI-RS configuration for Idle/inactive mode UE | Lenovo, Motorola Mobility |
| R2-2110353 | Discussion on dedicated signaling of TRS/CSI-RS configuration | Sony |
| R2-2110403 | TRS/CSI-RS SI update mechanism for DRX and eDRX Ues | CATT |
| R2-2110404 | Configurations for RLM/BFD Relaxation | CATT |
| R2-2110414 | Other aspects on UE power saving | Ericsson |
| R2-2110416 | Provisioning of TRS occasions to Idle and Inactive UEs | Ericsson |
| R2-2110540 | Discussion on potential TRS/CSI-RS | Huawei, HiSilicon |
| R2-2110541 | Discussion on criteria for the RLM/BFD relaxation | Huawei, HiSilicon |
| R2-2110619 | Initial Consideration on DCI based Power Saving | ZTE Corporation,Sanechips |
| R2-2110820 | Potential TRS/CSI-RS occasion(s) | Nokia, Nokia Shanghai Bell |
| R2-2111034 | RAN2 impact on connected mode power saving | Nokia, Nokia Shanghai Bell |
| R2-2111285 | Summary of agenda 8.9.3: Other aspects RAN2 impacts - TRS CSI-RS for RRC-IDLE and RRC-INACTIVE | Apple |
| R2-2111528 | Summary of [AT116-e][036][ePowSav] RLM/BFD relaxation (Xiaomi) | Xiaomi |
| 8.10.1 | Organizational | |
| R2-2109307 | LS on extended NAS supervision timers at satellite access (C1-215074; contact: Ericsson) | CT1 |
| R2-2109312 | Reply LS on TA pre-compensation (R1-2108410; contact: OPPO) | RAN1 |
| R2-2109373 | LS Response to Reply LS on UE location aspects in NTN (S2-2106651; contact: Qualcomm) | SA2 |
| R2-2109586 | Support Non-Terrestrial Networks | THALES |
| R2-2109815 | Reply LS on UE location aspects in NTN (C1-216250; contact: Nokia) | CT1 |
| R2-2110466 | Stage-3 running 304 CR for NTN | ZTE corporation, Sanechips |
| R2-2110710 | Stage-3 running RRC CR for NTN Rel-17 | Ericsson |
| R2-2110863 | MAC open issues in NTN - RAN2#116e | InterDigital |
| R2-2110864 | Stage 3 NTN running CR for 38.321 - RAN2#116e | InterDigital |
| R2-2111221 | LS on UE TA reporting (R1-2110663; contact: Ericsson) | RAN1 |
| R2-2111336 | Support Non-Terrestrial Networks | THALES |
| R2-2111337 | Stage-3 running RRC CR for NTN Rel-17 | Ericsson |
| R2-2111367 | Summary of [Post116-e][101][NTN] Stage 2 running CR (Thales) | Thales |
| R2-2111544 | Summary of [AT116-e][107][NTN] Stage 2 running CR (Thales) | Thales |
| R2-2111613 | Support Non-Terrestrial Networks | THALES |
| R2-2111614 | Stage-3 running RRC CR for NTN Rel-17 | Ericsson |
| R2-2111615 | Stage-3 running CR for TS 38.321 for Rel-17 NTN | InterDigital |
| R2-2111616 | Stage-3 running 304 CR for NTN | ZTE Corporation, Sanechips |
| R2-2111617 | Stage-3 running CR for TS 38.322 for Rel-17 NTN | MediaTek |
| R2-2111618 | Stage-3 running CR for TS 38.323 for Rel-17 NTN | MediaTek |
| 8.10.2.1 | RACH aspects | |
| R2-2109498 | Discussion on RACH and TA report in NTN | OPPO |
| R2-2109551 | Discussion on UE-specific TA information reporting in NTN | CATT |
| R2-2109660 | Further consideration on TA reporting | Huawei, HiSilicon |
| R2-2110018 | RACH Type selection and TA report | Xiaomi |
| R2-2110019 | RACH Type selection and TA report | Xiaomi |
| R2-2110044 | UE Reported UE Specific TA Pre-Compensation | Apple |
| R2-2110125 | TA report procedure | Spreadtrum Communications |
| R2-2110703 | Reporting information about UE specific TA and RA Type Selection | Nokia, Nokia Shanghai Bell |
| R2-2110733 | Remaining issues on TA report | ZTE Corporation, Sanechips |
| R2-2110765 | TA reporting Remaining issues | NEC Telecom MODUS Ltd. |
| R2-2110774 | Further considerations on TA report | Samsung Research America |
| R2-2110941 | Additional criterion for RA type selection | Samsung Research America |
| R2-2110952 | Reporting information about UE specific TA pre-compensation in NTNs | Ericsson |
| R2-2111005 | Discussion on LCH-based RA type selection | ASUSTeK |
| R2-2111006 | Discussion on issue of restarting contention resolution timer | ASUSTeK |
| R2-2111140 | Discussion on RACH and TA report aspects | LG Electronics Inc. |
| R2-2111207 | Discussion on UE-specific TA information reporting in NTN | CATT |
| R2-2111338 | Summary of [AT116-e][106][NTN] RACH aspects (OPPO) | OPPO |
| R2-2111351 | Summary of [AT116-e][106][NTN] RACH aspects (OPPO) – phase 2 | OPPO |
| 8.10.2.2 | Other MAC aspects | |
| R2-2109499 | Discussion on HARQ related aspects in NTN | OPPO |
| R2-2109552 | Co-existence issue of BSR over CG and BSR over 2-step RA | CATT |
| R2-2109631 | Remaining issue on disabling uplink HARQ retransmission | MediaTek Inc. |
| R2-2109632 | Round trip delay offset for configured grant timers | MediaTek Inc. |
| R2-2109661 | Further consideration on LCP and HARQ | Huawei, HiSilicon |
| R2-2109922 | On Updating SR-Prohibit Timer in NR-NTN | MediaTek Inc. |
| R2-2109968 | HARQ process for SPS and CG | Qualcomm Incorporated |
| R2-2110017 | Remaining issues related to HARQ retransmission state | Xiaomi |
| R2-2110045 | NTN HARQ Management | Apple |
| R2-2110126 | Discussion on HARQ and LCP remaining issues | Spreadtrum Communications |
| R2-2110308 | Remaining UP issues for NR NTN | Lenovo, Motorola Mobility |
| R2-2110354 | CG enhancements in NTN | Sony |
| R2-2110704 | Discussion on UL scheduling, DRX and other MAC aspects | Nokia, Nokia Shanghai Bell |
| R2-2110734 | Remaining issues on HARQ aspects | ZTE Corporation, Sanechips |
| R2-2110859 | Remaining MAC open issues in NTN | InterDigital |
| R2-2110926 | Updating SR-Prohibit Timer | MediaTek Inc. |
| R2-2110951 | On configured scheduling, DRX, LCP, HARQ and SR/BSR in NTNs | Ericsson |
| R2-2111044 | Remaining Issue on LCP Restrictions and CG Impact in NTN | CMCC |
| R2-2111139 | Discussion on other MAC aspects | LG Electronics Inc. |
| R2-2111151 | Retransmission timer for HARQ state B | ITL |
| R2-2111154 | HARQ State A/B for CG aspects | ITL |
| R2-2111267 | Remaining issue on disabling uplink HARQ retransmission | MediaTek Inc. |
| R2-2111331 | [101][NTN] Summary on remaining aspects of timers, HARQ, and LCP including CG/SPS aspects in AI 8.10.2.2 | Interdigital |
| R2-2111339 | Summary of [AT116-e][101][NTN] Other MAC aspects | InterDigital (summary rapporteur) |
| R2-2111354 | [offline-101] Other MAC aspects - second round | Interdigital |
| 8.10.2.3 | RLC and PDCP aspects | |
| R2-2110548 | Consequences of long propagation delays on RLC | Interdigital, Inc. |
| R2-2110766 | RLC t-Reassembly timer | NEC Telecom MODUS Ltd. |
| R2-2110925 | On RLC t-Reassembly for NTN | Sequans Communications |
| R2-2110950 | On RLC and PDCP for NTNs | Ericsson |
| 8.10.3.1 | General aspects | |
| R2-2109500 | Discussion on T300’s extension in NTN | OPPO |
| R2-2109553 | Discussion on UE coarse location information report in NTN | CATT |
| R2-2109587 | Validity timer of a broadcasted TAC | THALES, Ericsson |
| R2-2109636 | Consideration on RAN2-determined NTN UE capabilities | Intel Corporation |
| R2-2109969 | Coarse UE location report in RRC_CONNECTED | Qualcomm Incorporated |
| R2-2109973 | Discussion on UE reporting of selected TAI | vivo, Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2109974 | Discussion on UE capability for Rel-17 NR NTN | vivo |
| R2-2109975 | Discussion on the remaining issue on TAC update | vivo |
| R2-2110127 | Discussion on stop serving time of NTN cell | Spreadtrum Communications |
| R2-2110136 | Discussion on TAC update in NTN | Spreadtrum Communications |
| R2-2110355 | Event triggered location reporting in NTN | Sony |
| R2-2110386 | DRAFT Reply LS on extended NAS supervision timers at satellite access | Ericsson |
| R2-2110388 | Discussion on reply LS to CT1 on extended NAs supervision timers at satellite access | Ericsson |
| R2-2110467 | UE location report and TAC in NTN | ZTE corporation, Sanechips |
| R2-2110528 | Further considerations on TAC selection in NTN | Samsung R&D Institute UK |
| R2-2110614 | Final views on location aspects for Rel-17 NTN | Nokia, Nokia Shanghai Bell |
| R2-2111007 | Discussion on event triggered based UE location report | ASUSTeK |
| R2-2111043 | Discussion on UE Coarse Location Information Report in NTN | CMCC |
| R2-2111110 | Discussion on UE location reporting in NTN | Xiaomi |
| R2-2111342 | [offline-108] Extended NAS timers (Ericsson) | Ericsson |
| R2-2111343 | Draft Reply on UE location aspects in NTN | Qualcomm |
| R2-2111357 | Draft Reply on UE location aspects in NTN | Qualcomm |
| R2-2111358 | DRAFT Reply LS on extended NAS supervision timers at satellite access | Ericsson |
| R2-2111454 | Draft Reply on UE location aspects in NTN | Qualcomm |
| R2-2111546 | Reply LS on extended NAS supervision timers at satellite access | RAN2 |
| R2-2111547 | Reply on UE location aspects in NTN | RAN2 |
| R2-2111612 | Reply LS on extended NAS supervision timers at satellite access | RAN2 |
| 8.10.3.2 | Idle/Inactive mode | |
| R2-2109501 | Discussion on idle/inactive mode procedures in NTN | OPPO |
| R2-2109554 | Further Discussion on the Leftover Issues of IDLE/INACTIVE | CATT |
| R2-2109637 | Discussion on enhancements to cell reselection | Intel Corporation |
| R2-2109639 | Discussion on TN prioritization over NTN for idle mode | Intel Corporation |
| R2-2109765 | Cell selection and reselection enhancements for NTN | China Telecom |
| R2-2109970 | Enhancement to cell selection and reselection | Qualcomm Incorporated |
| R2-2109976 | Remaining issues on cell reselection for NTN | vivo |
| R2-2110043 | NTN Ephemeris definition and signaling | Apple |
| R2-2110046 | NTN Cell Selection and Cell Reselection | Apple |
| R2-2110211 | NTN-TN Mobility Enhancement in IDLE and INACTIVE State | FGI, Asia Pacific Telecom |
| R2-2110228 | Remaining issues in NTN idle mode | LG Electronics Inc. |
| R2-2110265 | Discussion on cell reselection | CMCC |
| R2-2110275 | Discussion on cell reselection | Huawei, HiSilicon |
| R2-2110309 | Considerations on ephemeris provision for NTN | Lenovo, Motorola Mobility |
| R2-2110356 | Idle mode enhancement in NTN | Sony |
| R2-2110375 | Idle mode aspects for NTN | Ericsson |
| R2-2110468 | Consideration on the system information and idle mode mobility for intra-NTN and TN-NTN case | ZTE corporation, Sanechips |
| R2-2110768 | NTN to TN mobility in Idle or Inactive mode | NEC Telecom MODUS Ltd. |
| R2-2110769 | Time and Location-assisted cell reselection | NEC Telecom MODUS Ltd. |
| R2-2110862 | Cell reselection for earth moving cells | InterDigital |
| R2-2110943 | Further considerations on idle/inactive behaviours | Samsung Research America |
| R2-2111111 | Cell selection and reselection enhancements for NTN | Xiaomi |
| R2-2111332 | [102][NTN] Summary of cell (re)selection aspects in AI 8.10.3.2 | Intel |
| R2-2111341 | Summary of [AT116-e][102][NTN] Idle mode aspects (Intel) | Intel |
| R2-2111352 | [offline-102] Idle mode aspects - second round | Intel |
| 8.10.3.3 | Connected mode | |
| R2-2109502 | Discussion on mobility management for connected mode UE in NTN | OPPO |
| R2-2109555 | Futher discussion on NTN mobility aspect | CATT |
| R2-2109634 | Efficient Configuration of SMTC and Measurement Gaps in NR-NTN | MediaTek Inc. |
| R2-2109635 | Mobility for NTN-TN scenarios | MediaTek Inc. |
| R2-2109638 | Discussion on remaining issues on SMTC | Intel Corporation |
| R2-2109971 | Open issues in CHO | Qualcomm Incorporated |
| R2-2109972 | SMTC and MG enhancements | Qualcomm Incorporated |
| R2-2109977 | Remaining issues on connected mode mobility for NTN | vivo |
| R2-2110229 | Remaining issues in NTN CHO | LG Electronics Inc. |
| R2-2110266 | Further discussion on intra-NTN mobility | CMCC |
| R2-2110267 | Further discussion on SMTC and measurement Gap configuration for NTN | CMCC |
| R2-2110276 | Discussion on CHO in NTN | Huawei, HiSilicon |
| R2-2110277 | Discussion on SMTC and measurement gap configuration | Huawei, HiSilicon |
| R2-2110283 | Discussion on signaling and data transmission issues of NTN CHO | ITRI |
| R2-2110310 | UE assistance for measurement gap and SMTC configuration in NTN | Lenovo, Motorola Mobility |
| R2-2110311 | Connected mobility for NTN/TN continuity | Lenovo, Motorola Mobility |
| R2-2110312 | Remaining issues for CHO in NTN | Lenovo, Motorola Mobility |
| R2-2110340 | Connected mode aspects for NTN | Ericsson |
| R2-2110357 | SMTC enhancement in NTN | Sony |
| R2-2110358 | Signaling storm during HOs | Sony |
| R2-2110384 | SMTC and measurement gap enhancements | LG Electronics Inc. |
| R2-2110469 | Consideration on CHO and measurements | ZTE corporation, Sanechips |
| R2-2110612 | More thoughts on mobility in Rel-17 NTN | Nokia, Nokia Shanghai Bell |
| R2-2110613 | Final views on SMTC and measurement gaps for Rel-17 NTN | Nokia, Nokia Shanghai Bell |
| R2-2110815 | Measurements and handover | Samsung Research America |
| R2-2110860 | UE location reporting in NTN | InterDigital |
| R2-2110861 | UE-specific TA reporting in connected mode | InterDigital |
| R2-2111028 | Discussion on connected mode aspects for NTN | Xiaomi Communications |
| R2-2111166 | Remaining Issues on SMTC and measurement Gap configuration for NTN | Rakuten Mobile, Inc |
| R2-2111333 | [103][NTN] Summary of SMTC/gaps aspects in AI 8.10.3.3 | Nokia |
| R2-2111340 | [AT116-e][103][NTN] SMTC and gaps (Nokia) | Nokia, Nokia Shanghai Bell |
| R2-2111353 | [offline-103] SMTC and gaps | Nokia |
| 8.11.1 | Organizational | |
| R2-2109316 | Reply LS on determination of location estimates in local co-ordinates (R1-2108509; contact: Ericsson) | RAN1 |
| R2-2109322 | LS to RAN2 on SRS for Positioning Transmission by UEs in RRC_INACTIVE State (R1-2108564; contact: Intel) | RAN1 |
| R2-2109328 | LS on PRS measurement outside the measurement gap (R1-2108639; contact: Huawei) | RAN1 |
| R2-2109329 | LS on beam/antenna information for DL AOD in NR positioning (R1-2108646; contact: Ericsson) | RAN1 |
| R2-2109339 | Reply LS on determination of location estimates in local co-ordinates (R3-214312; contact: Huawei) | RAN3 |
| R2-2109345 | Reply LS on Positioning Reference Units (R3-214457; contact: Ericsson) | RAN3 |
| R2-2109392 | Liaison Note to 3GPP RAN 2, Reply comments to letter R2-2106596 (RTCM Paper 2021-SC134-0113) | RTCM |
| R2-2109480 | [Draft] Response LS on the Positioning Reference Units (PRUs) for positioning enhancement | CATT |
| R2-2109673 | Email discussion report on [609][POS] RAT-dependent stage 2 CR (Intel) | Intel Corporation |
| R2-2109674 | Email discussion [609] Running 38.305 CR for Positioning WI on RAT dependent positioning methods | Intel Corporation |
| R2-2109807 | Discussion RTCM reply to RAN2 on GNSS integrity coordination | ESA, Intel Corporation |
| R2-2110803 | Beam/antenna information for DL AOD in NR positioning | Ericsson |
| R2-2110997 | Email discussion report on [614][POS] GNSS Positioning Integrity Stage 2 CR (InterDigital) | InterDigital, Inc. |
| R2-2111012 | Running CR of 38.305 for GNSS Positioning Integrity | InterDigital, Inc. |
| R2-2111013 | Running CR of 36.305 for GNSS Positioning Integrity | InterDigital, Inc. |
| R2-2111211 | LS on support of SP-SRS for positioning by RRC_INACTIVE UEs (R1-2110598; contact: Intel) | RAN1 |
| R2-2111216 | LS on DL PRS reception priority by RRC_INACTIVE Ues (R1-2110644; contact: Intel) | RAN1 |
| R2-2111361 | Email discussion on LS to RTCM for GNSS integrity | ESA |
| R2-2111374 | Email discussion [609] Running 38.305 CR for Positioning WI on RAT dependent positioning methods | Intel Corporation |
| R2-2111375 | Report of offline discussion [AT116-e][623][POS] 38.305 CR for RAT-dependent positioning (Intel) | Intel Corporation |
| R2-2111376 | Running CR of 36.305 for GNSS Positioning Integrity | InterDigital, Inc. |
| R2-2111377 | Running CR of 38.305 for GNSS Positioning Integrity | InterDigital, Inc. |
| R2-2111378 | Email discussion report on [AT116-e][624][POS] 36.305 and 38.305 CRs for GNSS positioning integrity (InterDigital) | InterDigital Inc. |
| R2-2111447 | Running CR of 36.305 for GNSS Positioning Integrity | InterDigital, Inc. |
| R2-2111448 | Running CR of 38.305 for GNSS Positioning Integrity | InterDigital, Inc. |
| R2-2111636 | Running 38.305 CR for Positioning WI on RAT dependent positioning methods | Intel Corporation |
| 8.11.2 | Latency enhancements | |
| R2-2109460 | Discussion on positioning latency reduction | ZTE |
| R2-2109481 | Discussion on Enhancements for Latency Reduction | CATT |
| R2-2109663 | Leftover issues on Latency reduction | Intel Corporation |
| R2-2109665 | Summary of [Post115-e][605][POS] Pre-configured assistance data (Intel) | Intel Corporation |
| R2-2109824 | Positioning Latency Reduction Enhancements | Lenovo, Motorola Mobility |
| R2-2109915 | Time T and Measurement Gap for Measurement Time Window | Ericsson |
| R2-2109978 | Discussion on latency enhancement | vivo |
| R2-2110103 | Further consideration of positioning latency enhancements | OPPO |
| R2-2110178 | Discussion on latency reduction techniques from other groups | Huawei, HiSilicon |
| R2-2110179 | Text Proposal for finer granularity of responseTime | Huawei, HiSilicon |
| R2-2110180 | Discussion on pre-configured PRS | Huawei, HiSilicon |
| R2-2110336 | Discussion on the response time | Samsung |
| R2-2110359 | Considerations on positioning latency | Sony |
| R2-2110798 | PRS Measurements outside measurement Gap | Ericsson |
| R2-2110822 | Remaining Issues on Scheduling Location in Advance | Qualcomm Incorporated |
| R2-2110928 | Discussion on Enhancements for Latency Reduction | InterDigital, Inc. |
| R2-2111075 | Discussion on the priority rule for latency reduction | CMCC |
| R2-2111081 | Simulation study for multiple QoS class handling for latency reduction | Samsung Electronics |
| R2-2111083 | Handling of multiple QoS for latency reduction | Samsung Electronics |
| R2-2111084 | Discussion on the Pre-configured Assistance Data | Samsung Electronics |
| R2-2111086 | Latency reduction via configured grant for positioning | Samsung Electronics |
| R2-2111105 | Positioning enhancements on latency reduction | Xiaomi |
| R2-2111252 | Summary of agenda 8.11.2: Latency enhancements | Samsung |
| 8.11.3 | RRC_INACTIVE | |
| R2-2109461 | Discussion on positioning in RRC INACTIVE state | ZTE |
| R2-2109482 | Discussion on UL NR positioning in RRC_INACTIVE | CATT |
| R2-2109758 | Supporting positioning in RRC_INACTIVE state | OPPO |
| R2-2109759 | Discussion on UL Positioning methods in RRC_INACTIVE state | OPPO |
| R2-2109825 | On Positioning in RRC_INACTIVE state | Lenovo, Motorola Mobility |
| R2-2109918 | Discussion on RRC Inactive mode Positioning | Ericsson |
| R2-2109979 | Summary of [Post115-e][608][POS] PRS configuration and measurement in RRC_INACTIVE | vivo |
| R2-2109980 | Discussion on UL positioning in RRC_INACTIVE | vivo |
| R2-2110021 | Support of UL&UL+DL positioning in RRC_INACTIVE | Intel Corporation |
| R2-2110174 | Way-forward for RRC_INACTIVE positioning | Huawei, CATT, China Unicom, CMCC, Fraunhofer, Futurewei, HiSilicon, Intel Corporation, Spreadtrum Communications, OPPO, VIVO, Xiaomi, ZTE Corporation |
| R2-2110249 | UE Positioning in RRC_INACTIVE mode | Fraunhofer IIS; Fraunhofer HHI |
| R2-2110337 | Discussion on the measurement reporting in RRC_INACTIVE | Samsung |
| R2-2110360 | Considerations on positioning RRC Inactive | Sony |
| R2-2110823 | Remaining issues for positioning of UEs in RRC_INACTIVE State | Qualcomm Incorporated |
| R2-2110824 | [draft] LS on DL-only and RAT-Independent Positioning in RRC_INACTIVE State | Qualcomm Incorporated |
| R2-2110929 | Discussion on Positioning in RRC INACTIVE state | InterDigital, Inc. |
| R2-2110930 | Discussion on reporting of positioning information using SDT | InterDigital, Inc. |
| R2-2111076 | Considerations on Positioning in RRC_INACTIVE state | CMCC |
| R2-2111106 | Discussion on positioning for UEs in RRC Inactive | Xiaomi |
| R2-2111251 | Summary for AI 8.11.3 on positioning in RRC_INACTIVE | OPPO |
| R2-2111379 | [AT116-e][625][POS] Proposals from RRC_INACTIVE positioning summary | OPPO |
| 8.11.4 | On-demand PRS | |
| R2-2109462 | Discussion on on-demand PRS | ZTE |
| R2-2109483 | Report of [Post115-e][606][POS] MO-LR for on-demand PRS (CATT) | CATT |
| R2-2109484 | Discussion on on-demand PRS | CATT |
| R2-2109664 | Support of On-Demand PRS request | Intel Corporation |
| R2-2109757 | Discussion on on-demand DL-PRS | OPPO |
| R2-2109826 | Support of On-Demand DL-PRS | Lenovo, Motorola Mobility |
| R2-2109916 | On demand PRS | Ericsson |
| R2-2109981 | Discussion on on-demand PRS | vivo |
| R2-2110040 | Stage-2 procedure for on-demand PRS | Apple |
| R2-2110175 | Discussion on on-demand PRS | Huawei, HiSilicon |
| R2-2110247 | On-demand PRS | Fraunhofer IIS, Fraunhofer HHI |
| R2-2110361 | Considerations on positioning PRS On-demand | Sony |
| R2-2110825 | Remaining issues for on-demand DL-PRS | Qualcomm Incorporated |
| R2-2110931 | Discussion on procedures for On-demand PRS for DL-based positioning | InterDigital, Inc. |
| R2-2110932 | Discussion on procedure for On-demand PRS for DL+UL based positioning | InterDigital, Inc. |
| R2-2110956 | Clarifications to on-demand PRS Stage 2 | Nokia, Nokia Shanghai Bell |
| R2-2110957 | UE-initiated on-demand PRS requests | Nokia, Nokia Shanghai Bell |
| R2-2110958 | Pre-configured assistance data for on-demand PRS | Nokia, Nokia Shanghai Bell |
| R2-2110966 | [Draft] LS on MO-LR for on-demand PRS | CATT |
| R2-2111090 | [Draft] LS on stage-2 on-demand PRS procedure | CATT |
| R2-2111107 | Positioning enhancement to on-demand DL PRS | Xiaomi |
| R2-2111256 | Summary of Agenda Item 8.11.4: On-demand PRS | Lenovo, Motorola Mobility |
| 8.11.5 | GNSS positioning integrity | |
| R2-2109463 | Discussion on positioning integrity | ZTE |
| R2-2109920 | On GNSS Integrity | Ericsson |
| R2-2109982 | Discussion on open issues for GNSS positioning integrity | vivo |
| R2-2110102 | Discussion on supporting positioing integrity in RAN | OPPO |
| R2-2110141 | Discussion on GNSS Integrity Assistance Data | Swift Navigation, Mitsubishi Electric Corporation, Intel Corporation, Ericsson |
| R2-2110176 | Remaining issues on positioning integrity | Huawei, HiSilicon |
| R2-2110181 | Summary of [Post115-e][607][POS] Integrity assistance data | Huawei, HiSilicon |
| R2-2110246 | UE-aided detection of threat to GNSS systems and assistance data signaling | Fraunhofer IIS; Fraunhofer HHI; Ericsson; ESA |
| R2-2110445 | On GNSS Positioning Integrity | Nokia, Nokia Shanghai Bell |
| R2-2110933 | Discussion on procedures and signalling for GNSS positioning integrity | InterDigital, Inc. |
| R2-2111087 | Consideration on the signalling design for Positioning Integrity | Samsung Electronics |
| R2-2111108 | Discussion on GNSS positioning integrity | Xiaomi |
| R2-2111263 | Summary of Agenda item 8.11.5- GNSS positioning integrity | CATT |
| R2-2111362 | LS to RTCM on GNSS integrity assistance data | ESA |
| R2-2111390 | LS to RTCM SC134 on GNSS integrity | RAN2 |
| R2-2111482 | Email discussion on LS to RTCM for GNSS integrity | ESA |
| 8.11.6 | A-GNSS enhancements | |
| R2-2109485 | Introduction of B2a and B3I signal in BDS system in A-GNSS | CATT, CAICT |
| R2-2109486 | Introduction of B2a and B3I signal in BDS system in A-GNSS | CATT, CAICT |
| R2-2109487 | Introduction of B2a signal in BDS system in A-GNSS | CATT, CAICT |
| R2-2109488 | Introduction of B3I signal in BDS system in A-GNSS | CATT, CAICT |
| R2-2111504 | Introduction of B2a signal in BDS system in A-GNSS | CATT, CAICT |
| R2-2111514 | [AT116-e][613][POS] BDS B2a and B3I signals (CATT) | CATT |
| 8.11.7 | Other | |
| R2-2109489 | Discussion on Positioning Reference Units(PRUs) | CATT, ZTE Coroporation, Intel Coroporation |
| R2-2109827 | Support of Positioning Reference Units | Lenovo, Motorola Mobility |
| R2-2109917 | On high accuracy aspects | Ericsson |
| R2-2109919 | On the Positioning Reference Units aspects | Ericsson |
| R2-2109983 | Discussion on support for positioning reference unit | vivo |
| R2-2110039 | Stage-3 impacts of PRU support | Apple |
| R2-2110177 | Discussion on PRU | Huawei, HiSilicon |
| R2-2110826 | Remaining issues for Positioning Reference Units | Qualcomm Incorporated |
| R2-2110827 | [draft] Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance | Qualcomm Incorporated |
| R2-2110934 | Discussion on supporting Positioning Reference Units | InterDigital, Inc. |
| R2-2111089 | Discussion on incoming LSs from RAN1 on positioning | vivo |
| R2-2111109 | Discussion on how to manage PRU | Xiaomi |
| R2-2111364 | Summary of [AT116-e][615][POS] PRUs | Qualcomm Incorporated (Moderator) |
| R2-2111488 | Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance | RAN2 |
| 8.12.1 | Organizational | |
| R2-2109305 | Reply LS on lower bound for eDRX cycle length (C1-214961; contact: Qualcomm) | CT1 |
| R2-2109325 | LS on RAN1 agreements on RAN2-led features for RedCap (R1-2108631; contact: NTT DOCOMO) | RAN1 |
| R2-2109342 | Reply LS on the coordination between gNBs on the supporting of RedCap UEs (R3-214422; contact: Ericsson) | RAN3 |
| R2-2109378 | Reply LS on introducing extended DRX for RedCap UEs (S2-2106978; contact: Qualcomm) | SA2 |
| R2-2109666 | Email discussion report on [108][RedCap] 38.306 Running CR (Intel) | Intel Corporation |
| R2-2109667 | Email discussion [108]Running 38.331 CR for the RedCap WI on capablities | Intel Corporation |
| R2-2109668 | Email discussion [108]Running 38.306 CR for the RedCap WI on capablities | Intel Corporation |
| R2-2109740 | Email discussion [109] Running MAC CR for RedCap | vivo (Rapporteur) |
| R2-2110727 | LS on use of NCD-SSB instead of CD-SSB for RedCap UE (R1-2110600; contact: Ericsson) | RAN1 |
| R2-2110821 | Running 38300 CR for RedCap | Nokia, Nokia Shanghai Bell |
| R2-2111095 | Running 38.304 CR for the RedCap WI | Ericsson |
| R2-2111097 | Running 38.331 CR for the RedCap WI | Ericsson |
| R2-2111102 | [Draft] LS reply on the coordination between gNBs supporting RedCap UEs | Ericsson |
| R2-2111215 | Reply LS on L2 buffer size reduction (R1-2110638; contact: Intel) | RAN1 |
| R2-2111233 | LS on introducing NR RedCap Indication (S2-2107853; contact: Ericsson) | SA2 |
| R2-2111347 | Running 38300 CR for RedCap | Nokia, Nokia Shanghai Bell |
| R2-2111349 | [Draft] LS reply on the coordination between gNBs supporting RedCap UEs | Ericsson |
| R2-2111360 | LS reply on the coordination between gNBs supporting RedCap Ues | RAN2 |
| R2-2111545 | Reply LS on the use of NCD-SSB instead of CD-SSB for RedCap UE | RAN2 |
| R2-2111619 | Running 38300 CR for RedCap | Nokia, Nokia Shanghai Bell |
| R2-2111620 | Running CR for the RedCap WI | Ericsson |
| R2-2111621 | Running CR for the RedCap WI | Ericsson |
| R2-2111628 | Running MAC CR for RedCap | vivo (Rapporteur) |
| R2-2111629 | Running 38.306 CR for the RedCap WI on capablities | Intel Corporation |
| 8.12.2.1 | Definition of RedCap UE type and reduced capabilities | |
| R2-2109446 | Support for fallback operation by RedCap UEs | Qualcomm Incorporated |
| R2-2109576 | Definition and reduced capabilities for RedCap UE, and NCD-SSB related LS | Huawei, HiSilicon |
| R2-2109669 | Open issues on RedCap capabilities | Intel Corporation |
| R2-2110093 | Optional support of more than 8 DRB for RedCap | Apple, Facebook Inc. |
| R2-2110134 | Discussion on L2 buffer size reduction for Redcap UE | Spreadtrum Communications |
| R2-2110709 | Discussion on reduced capabilities | LG Electronics UK |
| R2-2110771 | Definition of RedCap UE and discussion on capabilities | Ericsson |
| R2-2110881 | Discussion on L2 buffer size reduction | Sierra Wireless. S.A. |
| 8.12.2.2 | Identification, access and camping restrictions | |
| R2-2109447 | Reply LS to RAN3 on the coordination between gNBs on the supporting RedCap UEs | Qualcomm Incorporated |
| R2-2109448 | Reply LS on use of NCD-SSB instead of CD-SSB for RedCap UE | Qualcomm Incorporated |
| R2-2109451 | NCD-SSB and RedCap-specific BWPs | Qualcomm Incorporated |
| R2-2109494 | Discussion on early identification and access restrictions | OPPO |
| R2-2109536 | Cell barring aspects and early indication in Msg3_MsgA | Samsung Electronics Co., Ltd |
| R2-2109577 | Identification and access restriction of RedCap UE | Huawei, HiSilicon |
| R2-2109646 | Neighbour cell information and cell (re)selection for RedCap UE | DENSO CORPORATION |
| R2-2109670 | Early identification and camping restrictions for RedCap UE | Intel Corporation |
| R2-2109698 | Discussion on the remaining issues of early identification | CATT |
| R2-2109723 | Discussion on potential interference issues in networks partially supporting RedCap UE cell selection/re-selection | NEC Corporation |
| R2-2109741 | Discussion on NCD SSB and UE type for RedCap UEs | vivo, Guangdong Genius |
| R2-2109742 | Identification and access restrictions for RedCap UEs | vivo, Guangdong Genius |
| R2-2109752 | Camping restrictions of RedCap UE | Fujitsu |
| R2-2109819 | Discussion on UE access restrictions for Redcap devices | Beijing Xiaomi Mobile Softwar |
| R2-2109820 | Discussion on early Identification for Redcap devices | Beijing Xiaomi Mobile Softwar |
| R2-2109897 | Identification, access and camping restrictions for RedCap UE | ZTE Corporation, Sanechips |
| R2-2110094 | RA-RNTI overlap in RedCap and it’s impact on unified RACH work | Apple |
| R2-2110095 | Making ND-SSB work for RedCap in Rel-17 | Apple |
| R2-2110096 | System information indication for camping restrictions of RedCap UE | China Telecommunications |
| R2-2110135 | Discussion on the open issues of early indication for RedCap UE | Spreadtrum Communications |
| R2-2110202 | Access Restriction for RedCap UE | NTT DOCOMO INC. |
| R2-2110535 | Discussion on access restrictions and early identification | CMCC |
| R2-2110536 | Discussion on RAN3 LS | CMCC |
| R2-2110537 | Corrections for cellBarred in MIB handling for RedCap UE | InterDigital, Europe, Ltd. |
| R2-2110585 | Discussion on SI indication for camping restrictions for RedCap UEs | LG Electronics UK |
| R2-2110659 | Network behaviour for RedCap Msg3 and cell barring | BT plc |
| R2-2110664 | Access restrictions for RedCap | NEC |
| R2-2110773 | Use of NCD-SSB instead of CD-SSB for RedCap UEs | Ericsson |
| R2-2110793 | On RedCap UE behaviors when missing essential system information | Futurewei Technologies |
| R2-2110804 | On the use of NCD-SSB instead of CD-SSB for RedCap UE | MediaTek Inc. |
| R2-2110811 | REDCAP UE early identification | Nokia, Nokia Shanghai Bell |
| R2-2110880 | Early identification and camping restrictions for RedCap UE | Sierra Wireless. S.A. |
| R2-2111098 | Early indication & access restriction for RedCap UEs | Ericsson |
| R2-2111100 | Discussion on the coordination between gNBs supporting RedCap UEs | Ericsson |
| R2-2111150 | System Information and supporting for RedCap UEs | KDDI Corporation |
| R2-2111334 | Report - Using NCD-SSB instead of CD-SSB for RedCap Ues | Ericsson (Rapporteur) |
| R2-2111344 | Summary of [AT116-e][110][RedCap] Identification and access restriction | Huawei, HiSilicon |
| R2-2111348 | Report - Using NCD-SSB instead of CD-SSB for RedCap Ues - second round | Ericsson (Rapporteur) |
| R2-2111356 | Summary of [AT116-e][110][RedCap] Identification and access restriction - second round | Huawei, HiSilicon |
| R2-2111359 | Report of offline 113: Discussion for LS on inter-gNB coordination | Ericsson (Rapporteur) |
| R2-2111543 | Report - Using NCD-SSB instead of CD-SSB for RedCap Ues - third round | Ericsson (Rapporteur) |
| 8.12.3.1 | eDRX cycles | |
| R2-2109449 | Remaining issues on eDRX | Qualcomm Incorporated |
| R2-2109495 | Discussion on eDRX for RedCap Ues | OPPO |
| R2-2109537 | UE_ID for extended DRX cycle and SI update aspects | Samsung Electronics Co., Ltd |
| R2-2109578 | eDRX for RedCap UE | Huawei, HiSilicon |
| R2-2109649 | Discussion on e-DRX for Redcap Devices | Beijing Xiaomi Mobile Softwar |
| R2-2109671 | Leftover issues for eDRX | Intel Corporation |
| R2-2109699 | Further Discussion on eDRX for NR RRC Inactive and Idle | CATT |
| R2-2109743 | Discussion on eDRX for RedCap UEs | vivo, Guangdong Genius |
| R2-2109898 | Discussion on eDRX for RedCap UE | ZTE Corporation, Sanechips |
| R2-2110151 | Leftover issues on derivation of PTW_start | DENSO CORPORATION |
| R2-2110331 | Consideration on eDRX for RedCap UE | Lenovo, Motorola Mobility |
| R2-2110584 | Discussion on eDRX for RRC_IDLE and RRC_INACTIVE | LG Electronics UK |
| R2-2110755 | Remaining issues for eDRX | MediaTek Inc. |
| R2-2111099 | Extended DRX for Reduced Capability UEs | Ericsson |
| R2-2111129 | Remaining issues in paging monitoring | Samsung |
| R2-2111335 | Summary of [AT116-e][105][RedCap] eDRX cycles aspects (Apple) | Apple Inc. |
| R2-2111350 | Summary of [AT116-e][105][RedCap] eDRX cycles aspects (Apple) – Phase 2 | Apple Inc. |
| 8.12.3.2 | RRM relaxations | |
| R2-2109450 | Remaining issues on RRM relaxation | Qualcomm Incorporated |
| R2-2109496 | Discussion on RRM relax for RRC idle | OPPO |
| R2-2109497 | Discussion on RRM relax for RRC connected | OPPO |
| R2-2109575 | NR-REDCAP stationarity relaxations in case of RRC_CONNECTED | THALES |
| R2-2109579 | RRM measurement relaxation for RedCap UE | Huawei, HiSilicon |
| R2-2109588 | On the efficient RRM relaxation on RRC connected mode | Fraunhofer IIS, Fraunhofer HHI |
| R2-2109672 | RRM measurement relaxation for RedCap UE in RRC_CONNECTED | Intel Corporation |
| R2-2109700 | Further Discussion on RRM relaxations | CATT |
| R2-2109744 | RRM relaxation for neighboring cell for RedCap UEs | vivo, Guangdong Genius |
| R2-2109893 | Further discussion on RRM relaxation for RedCap UE | ZTE Corporation, Sanechips |
| R2-2110105 | RRM relaxation criterion of RedCap UE | China Telecommunications |
| R2-2110193 | Discussion on RRM measurement relaxation for redcap | Xiaomi Communications |
| R2-2110230 | Remaining issues in RRM relaxation | LG Electronics Inc. |
| R2-2110287 | RRM relaxation for RedCap UEs | SHARP Corporation |
| R2-2110564 | Details on RRM relaxation | Ericsson |
| R2-2110816 | On RRM relaxations for REDCAP | Nokia, Nokia Shanghai Bell |
| R2-2110817 | On RRM relaxations in CONNECTED | Nokia, Nokia Shanghai Bell |
| R2-2111130 | RRM measurement relaxation in RedCap | Samsung |
| R2-2111345 | [offline-111] RRM relaxation | Qualcomm |
| R2-2111355 | [offline-111] RRM relaxation - second round | Qualcomm |
| 8.13.1 | Organizational | |
| R2-2109334 | LS on Area scope configuration and Frequency band info in MDT configuration (R3-212824; contact: Huawei) | RAN3 |
| R2-2109335 | LS on UP measurements for Successful Handover Report (R3-212935; contact: Ericsson) | RAN3 |
| R2-2109336 | Reply LS on UE context keeping in the source cell (R3-212944; contact: Ericsson) | RAN3 |
| R2-2109343 | LS Reply on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions (R3-214429; contact: Ericsson) | RAN3 |
| R2-2109347 | MDT M6 calculation for split bearers in MR-DC (R3-214466; contact: Huawei) | RAN3 |
| R2-2109352 | LS on the Beam measurement reports for the MDT measurements (R3-214519; contact: Ericsson) | RAN3 |
| R2-2109388 | Reply LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions (S5-213499; contact: Ericsson) | SA5 |
| R2-2109391 | Reply LS on Report Amount for M4, M5, M6, M7 measurements (S5-214523; contact: Nokia) | SA5 |
| R2-2110846 | On beam information in immediate MDT measurement reports (reply LS R3-214519) | Ericsson |
| R2-2110884 | LS Reply On user plane masurements for successful handover report | Ericsson |
| R2-2111226 | Reply LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions (S5-215493; contact: Ericsson) | SA5 |
| R2-2111287 | Report of email discussion [AT116e][830][SON/MDT] Reply LS on Area scope configuration and Frequency band info in MDT configuration (Huawei) | Huawei |
| R2-2111288 | Reply LS on Area scope configuration and Frequency band info in MDT configuration | RAN2 |
| R2-2111289 | Report of email discussion [AT116e][831][SON/MDT] Reply LS on M6 calculation for split bearers in MR-DC (Huawei) | Huawei |
| R2-2111290 | Reply LS on MDT M6 calculation for split bearers in MR-DC | RAN2 |
| R2-2111476 | Reply LS on Beam measurement reports for the MDT measurements | RAN2 |
| R2-2111506 | [AT115e][832][SONMDT] Reply LS on Beam measurement reports (Ericsson) | Ericsson |
| 8.13.2.1 | Handover related SON aspects | |
| R2-2109562 | Discussion on SHR enhancements | vivo |
| R2-2109563 | Indication on the availability of rlf-Report via failureInformation for DAPS HO failure | vivo |
| R2-2110005 | Further Discussion on CHO and DAPS Aspects | CATT |
| R2-2110041 | UP measurements of HO interruption time | Apple |
| R2-2110097 | Further consideration of SON of HO related aspects | OPPO |
| R2-2110104 | Further consideration on successful handover report | OPPO |
| R2-2110256 | Open issues on SHR | NEC |
| R2-2110298 | SON Enhancements for CHO | Lenovo, Motorola Mobility |
| R2-2110299 | SON Enhancements for DAPS Handover | Lenovo, Motorola Mobility |
| R2-2110300 | SON Enhancements for SHR | Lenovo, Motorola Mobility |
| R2-2110529 | Remaining issues on SON Enhancement for CHO | CMCC |
| R2-2110530 | Remaining issues on SON Enhancement for DAPS | CMCC |
| R2-2110531 | Further Discussion on Successful Handover Report | CMCC |
| R2-2110635 | Discussion on handover related SON aspects | Huawei, HiSilicon |
| R2-2110717 | Further clarification on SON MRO | Nokia, Nokia Shanghai Bell |
| R2-2110735 | Remaining issues on HO related SON aspects | ZTE Corporation, Sanechips |
| R2-2110882 | Handover-related SON aspects | Ericsson |
| R2-2110889 | [Post115-e][899][SON/MDT] Handover related SON aspects (Ericsson) | Ericsson |
| R2-2110920 | HO related SON changes | QUALCOMM Technologies INC. |
| R2-2110936 | Discussion on CHO related RLF-Report | LG Electronics |
| R2-2110988 | SON Enhancements for CHO and DAPS HO | Samsung |
| R2-2110992 | SON Enhancements for Successful HO Report | Samsung |
| R2-2111016 | Discussion on HO type indicator for CHO and DAPS | SHARP Corporation |
| R2-2111024 | Discussion on contents of successful HO report | SHARP Corporation |
| R2-2111507 | [AT116-e][850][SONMDT] Handover related SON aspects again (Ericsson) | Ericsson |
| 8.13.2.2 | 2-step RA related SON aspects | |
| R2-2110006 | Report of [Post115-e][898][SON/MDT] 2-step RA related SON aspects | CATT |
| R2-2110007 | TS38.331 Draft CR for 2-step RA related SON aspects | CATT |
| R2-2110008 | Discussion on Signalling Structure of 2-step RA Report | CATT |
| R2-2110532 | Remaining issues on SON Enhancement for 2-step RA | CMCC |
| R2-2110636 | Discussion on 2 step RA related SON aspects | Huawei, HiSilicon |
| R2-2110736 | 2step RA related enhancements | ZTE Corporation, Sanechips |
| R2-2110837 | 2-Step RA information for SON purposes | Ericsson |
| R2-2110994 | SON Enhancements for 2SRA | Samsung |
| 8.13.2.3 | Other WID related SON features | |
| R2-2110009 | Further Analysis on UE RACH Report for SN | CATT |
| R2-2110010 | Further Analysis on PSCell MHI Enhancement | CATT |
| R2-2110301 | SON Enhancement for NR-U | Lenovo, Motorola Mobility |
| R2-2110637 | [Post115-e][897][SONMDT] Modeling aspects related to information required by SNSCG (Huawei) | Huawei |
| R2-2110638 | Discussion on other SON aspects | Huawei, HiSilicon |
| R2-2110716 | Discussion on other SON aspects | Nokia, Nokia Shanghai Bell |
| R2-2110719 | UE grouping impact on MRO | Nokia, Nokia Shanghai Bell |
| R2-2110737 | On other WID related issues | ZTE Corporation, Sanechips |
| R2-2110854 | On Other WID related SON features | Ericsson |
| R2-2110921 | NR-U Related Enhancements | QUALCOMM Technologies INC. |
| R2-2110995 | SON Enhancements: Others | Samsung |
| R2-2111299 | Report of email discussion [AT116e][820][SON/MDT] Information required by SNSCG (Huawei) | Huawei |
| 8.13.3.1 | Immediate MDT enhancements | |
| R2-2109564 | Discussions on RAN3 LS on immediate MDT | vivo |
| R2-2110639 | Discussion on M6 calculation for split bearers in MR-DC (RAN3 LS R2-2109347) | Huawei, HiSilicon |
| R2-2110640 | Discussion on immediate MDT enhancements | Huawei, HiSilicon |
| R2-2110718 | M5 Measurement for DC | Nokia, Nokia Shanghai Bell |
| R2-2110738 | Report of [Post115-e][895][SON/MDT] IMM MDT | ZTE Corporation, Sanechips |
| R2-2110739 | Consideration on immediate MDT enhancements | ZTE Corporation, Sanechips |
| R2-2110848 | On Immediate MDT Enhancements | Ericsson |
| R2-2111568 | Report of [AT116-e][851][SON/MDT] IMM MDT again (ZTE) | ZTE Corporation, Sanechips |
| 8.13.3.2 | Logged MDT enhancements | |
| R2-2110011 | Discussion on Logged MDT Enhancement | CATT |
| R2-2110042 | Remaining issues for logged MDT | Apple |
| R2-2110098 | Enhancements for logged MDT regarding RAT-specific coverage hole | OPPO |
| R2-2110533 | Further consideration on UL-DL coverage mismatch | CMCC |
| R2-2110641 | Discussion on logged MDT enhancements | Huawei, HiSilicon |
| R2-2110714 | Report on [Post115-e][896][SON/MDT] Logged MDT (Nokia) | Nokia, Nokia Shanghai Bell |
| R2-2110715 | Logged MDT and other enhancements | Nokia, Nokia Shanghai Bell |
| R2-2110740 | CEF report enhancements | ZTE Corporation, Sanechips |
| R2-2110850 | On logged MDT related enhancements | Ericsson |
| R2-2110923 | Logged measurement Enhancements | QUALCOMM Technologies INC. |
| R2-2110999 | SON Enhancements for SI Request Optimization | Samsung |
| R2-2111168 | Discussion on Logged MDT issues | Samsung Electronics Co., Ltd |
| 8.13.4 | L2 Measurements | |
| R2-2110242 | Introducion of PRB usage based on statistical MIMO layer | CMCC |
| R2-2110642 | Discussion on L2M | Huawei, CMCC, HiSilicon |
| R2-2110741 | L2 measurements enhancements | ZTE Corporation, Sanechips |
| R2-2110849 | On layer-2 measurements | Ericsson |
| R2-2110959 | Introducion of PRB usage based on statistical MIMO layer | CMCC |
| R2-2111196 | Introduction of enhanced PRB Usage for MIMO | China Unicom |
| R2-2111202 | 38.314 CR to introduce the enhanced PRB Usage for MIMO | China Unicom |
| R2-2111300 | Report of email discussion [AT116e][852][SON/MDT] Packet “reliability” measurement for D1 (Huawei) | Huawei |
| R2-2111534 | PRB usage based on MIMO layer | CMCC |
| 8.14 | NR QoE | |
| R2-2111521 | RAN visible QoE | Qualcomm Incorporated |
| R2-2111522 | [Draft] LS on RAN visible QoE | Qualcomm Incorporated |
| 8.14.1 | Organizational | |
| R2-2109348 | Reply LS on QoE configuration and reporting related issues (R3-214471; contact: CMCC) | RAN3 |
| R2-2109351 | LS on RAN3 agreements for NR QoE (R3-214477; contact: China Unicom) | RAN3 |
| R2-2109372 | Reply LS on the mapping between service types and slice at application (S2-2106537; contact: Qualcomm) | SA2 |
| R2-2109382 | Reply LS on the mapping between service types and slice at application (S4-211225; contact: Qualcomm) | SA4 |
| R2-2109383 | LS on TS 28.404/TS 28.405 Clarification (S4-211234; contact: Qualcomm) | SA4 |
| R2-2109384 | LS Reply on requirement for configuration changes of ongoing QMC sessions (S4-211248; contact: Huawei) | SA4 |
| R2-2109385 | LS Reply on QoE report handling at QoE pause (S4-211290; contact: Huawei) | SA4 |
| R2-2109386 | Reply LS on QoE configuration and reporting related issues (S4-211291; contact: Huawei) | SA4 |
| R2-2109389 | Reply LS on QoE report handling at QoE pause (S5-214519; contact: Huawei) | SA5 |
| R2-2109390 | Reply LS on QoE configuration and reporting related issues (S5-214520; contact: Huawei) | SA5 |
| R2-2109865 | Running RRC CR for QoE measurements | Ericsson |
| R2-2111064 | Running CR of UE capability for NR QoE | CMCC |
| R2-2111162 | 38.300 running CR for Introduction of QoE measurements in NR | China Unicom, Huawei, HiSilicon |
| R2-2111225 | Reply LS on QoE Reference and maximum number of QoE configurations in RRC (S5-215213; contact: Huawei) | SA5 |
| R2-2111633 | Running RRC CR for QoE measurements | Ericsson India Private Limited |
| R2-2111634 | 38.300 running CR for Introduction of QoE measurements in NR | China Unicom, Huawei, HiSilicon |
| R2-2111650 | Running RRC CR for QoE measurements | Ericsson |
| 8.14.2.1 | Configuration architecture general aspects | |
| R2-2109565 | QoE configuration, reporting and mobility | Qualcomm Incorporated |
| R2-2109662 | QoE measurement configuration and general aspects | Intel Corporation |
| R2-2109832 | Further discussion on transmission of QoE reports | Lenovo, Motorola Mobility |
| R2-2109866 | Configuration and reporting of QoE measurements | Ericsson |
| R2-2109867 | QoE measurements at handover, resume and re-establishment | Ericsson, China Unicom |
| R2-2109984 | Discussion on QoE configuration | vivo |
| R2-2110073 | Supporting mobility for NR QoE | Apple |
| R2-2110074 | RRC segmentation for NR QoE | Apple |
| R2-2110099 | Discussion on QoE measurement collection in NR | OPPO |
| R2-2110605 | Discussion on QoE measurement configuration and reporting | Huawei, HiSilicon |
| R2-2110606 | QoE handling during UE mobility | Huawei, HiSilicon |
| R2-2110609 | Draft reply LS on QoE configuration and reporting related issues | Huawei, HiSilicon |
| R2-2110720 | QoE configuration handling | Nokia, Nokia Shanghai Bell |
| R2-2110991 | Discussion on NR QoE configuration | ZTE Corporation, Sanechips |
| R2-2110993 | Discussion on NR QoE configuration | CATT |
| R2-2111062 | Remaining issues on configuration and reporting | CMCC |
| R2-2111132 | QoE configuration in general aspects | Samsung |
| R2-2111133 | RRC segmentation for QoE configuration and report | Samsung |
| R2-2111188 | Discussion on NR QoE measurement and configurations | China Unicom |
| R2-2111536 | Feature summary for 8.14.2.1 | Ericsson |
| R2-2111663 | LS on SA4 requirements for QoE | RAN2 |
| R2-2111665 | LS on SA4 requirements for QoE | RAN2 |
| 8.14.2.2 | Start and Stop | |
| R2-2109567 | QoE pause and resume handling | Qualcomm Incorporated |
| R2-2109574 | Draft reply LS on QoE report handling at QoE pause | Qualcomm Incorporated |
| R2-2109833 | Further discussion on QoE report handling at QoE pause | Lenovo, Motorola Mobility |
| R2-2109868 | Pause and resume of QoE measurements | Ericsson |
| R2-2109985 | Discussion on start and stop of QoE measurement | vivo |
| R2-2110075 | Pause/Resume functionality | Apple |
| R2-2110100 | [Draft] LS reply on further questions regarding QoE reporting handling at QoE pause | OPPO |
| R2-2110101 | Discussion on QoE measurement pausing and resuming | OPPO |
| R2-2110281 | Discussion on the partial QoE reporting and buffering at RAN overload | ITRI |
| R2-2110382 | QoE pause and resume procedure | LG Electronics Inc. |
| R2-2110608 | Discussion on SA4/SA5 reply for QoE pause | Huawei, HiSilicon |
| R2-2110721 | QoE stop and pause | Nokia, Nokia Shanghai Bell |
| R2-2110722 | RAN control on QoE reporting | Nokia, Nokia Shanghai Bell |
| R2-2110989 | Discussion on NR QoE start and stop | ZTE Corporation, Sanechips |
| R2-2110990 | Discussion on buffer for NR QoE start and stop | ZTE Corporation, Sanechips |
| R2-2110996 | Discussion on QoE collection start and stop | CATT |
| R2-2111131 | Pause and resume in QoE | Samsung |
| R2-2111512 | Report of offline discussion: [AT116-e][043][eQOE] QoE report handling at QoE pause | Huawei, HiSilicon |
| R2-2111513 | Further reply on QoE report handling at QoE pause | Huawei |
| 8.14.3 | Other | |
| R2-2109568 | Support of RAN visible QoE and per-slice QoE | Qualcomm Incorporated |
| R2-2109986 | Discussion on other WI objectives | vivo |
| R2-2110607 | RAN visible QoE | Huawei, HiSilicon |
| R2-2111063 | Discussion on UE capability for NR QoE | CMCC |
| R2-2111191 | Discussion on RAN visible of QoE | China Unicom |
| R2-2111603 | LS on RAN visible QoE | RAN2 |
| 8.15.1 | Organizational | |
| R2-2109323 | Reply LS on SL DRX design (R1-2108580; contact: ZTE) | RAN1 |
| R2-2109324 | Reply LS on time gap information in SCI (R1-2108622; contact: OPPO) | RAN1 |
| R2-2109606 | RRC running CR for NR Sidelink enhancements | Huawei, HiSilicon |
| R2-2109607 | Summary of [POST115-e][713][V2X/SL] 38.331 running CR | Huawei, HiSilicon |
| R2-2110157 | Summary of [POST115-e][712][SL] Discussion on stage 3 open issues in 38.321 running CR | LG Electronics France |
| R2-2110158 | Running CR of TS 38.321 for Sidelink enhancement | LG Electronics France |
| R2-2111177 | Draft Reply LS on PC5 DRX for ProSe | LG Electronics France |
| R2-2111220 | Reply LS on SL resource selection with DRX (R1-2110662; contact: InterDigital) | RAN1 |
| R2-2111232 | Reply LS on Tx Profile (S2-2107840; contact: LGE) | SA2 |
| R2-2111237 | LS on PC5 DRX for ProSe (S2-2107979; contact: LGE) | SA2 |
| R2-2111416 | Summary of open issues for 38.331 running CR | Huawei, HiSilicon (Rapporteur) |
| R2-2111417 | RRC running CR for NR Sidelink enhancements | Huawei, HiSilicon |
| R2-2111418 | Summary of open issues for 38.321 running CR | LG Electronics Inc. (Rapporteur) |
| R2-2111419 | Running CR of TS 38.321 for Sidelink enhancement | LG Electronics France |
| R2-2111430 | Reply LS on time gap information in SCI | RAN2 |
| R2-2111431 | Reply LS on SL resource selection with DRX | RAN2 |
| R2-2111432 | Reply LS on Tx Profile | RAN2 |
| R2-2111433 | LS response on PC5 DRX for ProSe | RAN2 |
| R2-2111434 | Stage 2 Running CR of TS 38.300 for eSL | InterDigital |
| 8.15.2 | SL DRX | |
| R2-2109396 | Summary of [POST115-e][714] | OPPO |
| R2-2109397 | Discussion on R17 SL-DRX applicability to ProSe service | OPPO, ZTE, Apple, MediaTek, China Telecom, Spreadtrum, China Mobile, Huawei, HiSilicon |
| R2-2109415 | Discussion on DRX left issues | OPPO |
| R2-2109476 | SL DRX Configuration Reporting Mechanism for GC/BC | CATT |
| R2-2109477 | Left issues for Sidelink Unicast DRX | CATT |
| R2-2109478 | [POST115-e][716][V2X/SL] Identified FFS and open issues (CATT) | CATT |
| R2-2109608 | Considerations on sidelink DRX for groupcast and broadcast | Huawei, HiSilicon |
| R2-2109609 | Remaining issues of the sidelink DRX for unicast | Huawei, HiSilicon |
| R2-2109610 | Remaining issues of SL communication impact on Uu DRX | Huawei, HiSilicon |
| R2-2109643 | Discussion on SL DRX Command | SHARP Corporation |
| R2-2109720 | Further discussion on identified FFS/ open issues of unicast sidelink DRX overall flow | NEC Corporation |
| R2-2109722 | Discussion on DRX suspend/resume mechanism | NEC Corporation |
| R2-2109724 | DRX Active time, Sensing and Configuration aspects | Lenovo, Motorola Mobility |
| R2-2109800 | Discussion on remaining issues for SL DRX | ZTE Corporation, Sanechips |
| R2-2109801 | Further consideration on SL DRX configuration | ZTE Corporation, Sanechips |
| R2-2109812 | Further issues on SL DRX | Nokia, Nokia Shanghai Bell |
| R2-2109813 | Discussion on alignment of mode 1 resource allocation and active time of SL Rx UE in SL DRX | Nokia, Nokia Shanghai Bell |
| R2-2109847 | SL-DRX configuration for Unicast, Broadcast and Groupcast | Fraunhofer IIS, Fraunhofer HHI |
| R2-2109907 | Remaining aspects of SL DRX | Ericsson |
| R2-2109908 | Impact analysis between SL DRX and SL relay | Ericsson |
| R2-2109936 | Resource Allocation Considering DRX | InterDigital |
| R2-2109937 | Remaining aspects on SL DRX Timers | InterDigital |
| R2-2109938 | Confirmation of WA on HARQ RTT Based on SCI | InterDigital, Apple, Ericsson, Nokia, MediaTek, Fujitsu, Samsung, Sharp, vivo, Huawei, HiSilicon, Qualcomm, Convida, ZTE |
| R2-2109956 | Leftover aspects on SL DRX configuration | Intel Corporation |
| R2-2109957 | On SL DRX alignment | Intel Corporation |
| R2-2110061 | Discussion on remaining issues on SL Impact of Uu-DRX | Apple |
| R2-2110062 | Discussion on Remaining issues of SL DRX | Apple |
| R2-2110106 | Discussion on SL-DRX for ProSe | vivo, Ericsson, InterDigital Inc, Lenovo, Motorola Mobility, CATT, ASUSTek |
| R2-2110119 | Remaining issues on DRX Timers for SL Unicast | Spreadtrum Communications |
| R2-2110155 | Discussion on remaining issues and further consideration on SL DRX | LG Electronics France |
| R2-2110162 | Open issues on TX centric SL DRX | LG Electronics France |
| R2-2110223 | Discussion on Uu impact | Xiaomi |
| R2-2110224 | Discussion on Sidelink DRX for unicast | Xiaomi |
| R2-2110225 | Discussion on Sidelink DRX for broadcast and groupcast | Xiaomi |
| R2-2110273 | Remaining issues of SL DRX | MediaTek Inc. |
| R2-2110316 | DRX Active time, Sensing and Configuration aspects | Lenovo, Motorola Mobility |
| R2-2110650 | Remaining issues for sidelink DRX | vivo |
| R2-2110680 | Summary of [Post115-e][715][SL] Determination of DRX timer length and start time(vivo) | vivo |
| R2-2110747 | SL data transmission considering SL DRX active time | Nokia, Nokia Shanghai Bell |
| R2-2110937 | Further consideration on SL DRX and Uu DRX alignments | Samsung Research America |
| R2-2110938 | Open issues on SL DRX operation in groupcast | Samsung Research America |
| R2-2111008 | Discussion on remaining issues on Sidelink DRX | ASUSTeK |
| R2-2111065 | Remaining issues for SL DRX timers | Lenovo, Motorola Mobility |
| R2-2111119 | Discussion on Uu DRX and SL DRX Alignment | Qualcomm Finland RFFE Oy |
| R2-2111120 | Discussion on Blind Retransmissions with DRX in Mode 1 | Qualcomm Finland RFFE Oy |
| R2-2111121 | Discussion on RLF and PC5 RRC Connection with SL DRX | Qualcomm Finland RFFE Oy |
| R2-2111122 | Discussion on pool separation for SL DRX | LG Electronics France and ZTE |
| R2-2111204 | Remaining issues of the sidelink DRX for unicast | Huawei, HiSilicon |
| R2-2111420 | [AT116-e][703][V2X/SL] SL-DRX for ProSe (LG) | LG |
| R2-2111421 | [AT116-e][704][V2X/SL] Need of additional new considerations (NEC) | NEC |
| R2-2111422 | Summary of [AT116-e][705][V2X/SL] SL DRX for SL-CSI reception | Xiaomi |
| R2-2111423 | [AT116-e][706][V2X/SL] Candidate resource selection (including related HARQ RTT issues) (Huawei) | Huawei, HiSilicon (Rapporteur) |
| 8.15.3 | Resource allocation enhancements RAN2 scope | |
| R2-2109416 | Discussion on resource allocation enhancement | OPPO |
| R2-2109479 | Consideration on Resource Allocation Enhancements | CATT |
| R2-2109719 | Discussion on RAN2 impacts for supporting inter-UE coordination Scheme 1 with preferred resource set | NEC Corporation |
| R2-2109958 | On resource allocation and inter-UE coordination aspects | Intel Corporation |
| R2-2110063 | Discussion on resource allocation enhancements | Apple |
| R2-2110120 | Discussion on resource allocation enhancement for NR sidelink | Spreadtrum Communications |
| R2-2110156 | Power efficient resource allocation and Inter-UE coordination | LG Electronics France |
| R2-2110317 | Discussion on sidelink resource allocation enhancements | Lenovo, Motorola Mobility |
| R2-2110396 | Inter-UE Coordination for Sidelink Mode 2 Resource Allocation | Fraunhofer IIS, Fraunhofer HHI |
| R2-2110419 | Power Reduction for Sidelink Mode 2 Resource Allocation | Fraunhofer IIS, Fraunhofer HHI |
| R2-2110651 | Discussion on inter-UE coordination for sidelink mode-2 | vivo |
| R2-2110691 | General principles for resource allocation enhancements for SL mode 2 | Ericsson |
| R2-2110828 | Discussion on inter-UE coordination | ZTE Corporation, Sanechips |
| R2-2110940 | Resource pool configuration and selection of resource selection mechanism | Samsung Research America |
| 8.16.1 | Organizational | |
| R2-2109306 | Reply LS on limited service availability of an SNPN (C1-215046; contact: Nokia) | CT1 |
| R2-2109341 | Response LS on PWS Support over SNPN (R3-214402; contact: Nokia) | RAN3 |
| R2-2109371 | Reply LS on support of PWS over SNPN (S1-213120; contact: Huawei) | SA1 |
| R2-2109375 | Reply to LS on Group IDs for Network selection (GINs) (S2-2106708; contact: Ericsson) | SA2 |
| R2-2109380 | Reply to LS on support of PWS over SNPN (S3-213609; contact: Nokia) | SA3 |
| R2-2109692 | Draft CR for Enhancements for Private Networks | Qualcomm Incorporated |
| R2-2109814 | Reply LS on limited service availability of an SNPN (C1-216096; contact: CMCC) | CT1 |
| R2-2110364 | Draft Stage 2 CR: Non-Public Network enhancements | Nokia, Nokia Shanghai Bell |
| R2-2110365 | Draft RRC CR: Non-Public Network enhancements | Nokia, Nokia Shanghai Bell |
| R2-2110366 | RAN2 Work Plan for Enhancement for Private Network Support for NG-RAN | Nokia, China Telecom (Rapporteurs) |
| R2-2111241 | LS reply on limited service availability of an SNPN (S2-2108091; contact: vivo) | SA2 |
| R2-2111398 | Draft Stage 2 CR: Non-Public Network enhancements | Nokia, Nokia Shanghai Bell |
| R2-2111399 | Draft RRC CR: Non-Public Network enhancements | Nokia, Nokia Shanghai Bell |
| R2-2111645 | Draft CR for Enhancements for Private Networks | Qualcomm Incorporated |
| 8.16.2 | Support SNPN with subscription or credentials by a separate entity | |
| R2-2109411 | Support SNPN with subscription or credentials by a separate entity | OPPO |
| R2-2109559 | Further Consideration on Subscription or Credentials by CH | CATT |
| R2-2109685 | Consideration on the Separate Entity Supporting | ZTE Corporation, Sanechips |
| R2-2109805 | On supporting external credential access in SNPN | Samsung R&D Institute India |
| R2-2109987 | Remaining issue on supporting SNPN by a separate entity | vivo |
| R2-2110367 | SIB issues to support Credential Holders and onboarding | Nokia, Nokia Shanghai Bell |
| R2-2110902 | SNPN access using external credentials | Ericsson |
| R2-2110978 | Left issues on supporting External Credentials and UE onboarding | Huawei, HiSilicon |
| R2-2110979 | Discussion on GINs for SNPN | Huawei, HiSilicon, China Telecom |
| R2-2111047 | Left Issues on Supporting SNPN with Credentials by a Separate Entity | CMCC |
| R2-2111143 | GIn signaling | LG Electronics |
| 8.16.3 | Support UE onboarding and provisioning for NPN | |
| R2-2109412 | Support UE onboarding and provisioning for NPN | OPPO |
| R2-2109560 | Open issues on UE Onboarding and Provisioning for NPN | CATT |
| R2-2109615 | GINs for network selections | Intel Corporation |
| R2-2109686 | Consideration on the Onboarding and Provisioning for NPN | ZTE Corporation, Sanechips |
| R2-2109697 | Remaining issues of UE onboarding | Qualcomm Incorporated |
| R2-2109808 | On supporting onboarding and provisioning for SNPN | Samsung R&D Institute India |
| R2-2109988 | Remaining issue on support UE onboarding for NPN | vivo |
| R2-2110264 | Remaining Issues on supporting UE on-boarding and remote provisioning | CMCC |
| R2-2110368 | Cell selection for onboarding | Nokia, Nokia Shanghai Bell |
| R2-2110903 | UE onboarding | Ericsson |
| R2-2111144 | Open issues for UE Onboarding | LG Electronics |
| 8.16.4 | Other | |
| R2-2109413 | Support of IMS voice and emergency services for SNPN | OPPO |
| R2-2109561 | Open issues on Support of IMS Emergency for SNPN | CATT |
| R2-2109687 | Consideration on the emergency services for SNPN | ZTE Corporation, Sanechips |
| R2-2109704 | Support of emergency services and PWS for SNPN | Qualcomm Incorporated |
| R2-2109764 | Details of Support of IMS Voice and Emergency Services for SNPN | China Telecom, Huawei, HiSilicon |
| R2-2109810 | On supporting Emergency services in SNPN | Samsung R&D Institute India |
| R2-2109989 | Support of emergency service for SNPN | vivo |
| R2-2110261 | Support of emergency services for SNPN | CMCC |
| R2-2110369 | Considerations for IMS emergency support indicator | Nokia, Nokia Shanghai Bell |
| R2-2110904 | Support of emergency services and PWS for SNPNs | Ericsson |
| R2-2110980 | Support of IMS voice and emergency services for SNPN | Huawei, HiSilicon |
| R2-2111145 | Emergency service on SNPN | LG Electronics |
| 8.17.1 | Organizational | |
| R2-2109317 | LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN2 (R1-2108526; contact: Samsung) | RAN1 |
| R2-2109318 | LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN3 (R1-2108527; contact: Samsung) | RAN1 |
| R2-2109319 | LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN4 (R1-2108528; contact: Samsung) | RAN1 |
| R2-2109326 | LS on Rel-17 inter-cell multi TRP (R1-2108633; contact: vivo) | RAN1 |
| R2-2109364 | Reply LS on TCI state updates for L1/L2 centric inter-cell mobility R4-2115357; contact: Ericsson) | RAN4 |
| R2-2110666 | Running RRC CR for FeMIMO Rel-17 | Ericsson |
| R2-2110960 | MAC Running CR for Rel-17 feMIMO | Samsung |
| R2-2111214 | LS Reply on inter-cell beam management and multi-TRP in Rel-17 (R1-2110631; contact: Nokia) | RAN1 |
| R2-2111246 | LS on Re-17 LTE and NR higher-layers parameter list (R1-2110575; contact: Ericsson) | RAN1 |
| R2-2111596 | [DRAFT] LS on MPE information signalling | Nokia |
| R2-2111600 | LS on MPE information signalling | RAN2 |
| R2-2111662 | MAC Running CR for Rel-17 feMIMO | Samsung |
| 8.17.2 | Support of Inter-Cell beam management | |
| R2-2109573 | Discussion on inter-cell beam management | OPPO |
| R2-2109641 | Inter-cell BM and inter-cell mTRP | Intel Corporation |
| R2-2109745 | Discussion on inter-cell BM and RRC structure for inter-cell BM and mTRP | vivo |
| R2-2109746 | Discussion on inter-cell MTRP operation | vivo |
| R2-2109793 | Inter-cell beam management in RAN2 | Nokia, Nokia Shanghai Bell |
| R2-2110131 | Discussion on inter-cell beam management | Spreadtrum Communications |
| R2-2110167 | Inter-cell Beam Management and mTRP | Qualcomm Incorporated |
| R2-2110200 | Discussion on RLM for inter-cell Multi-TRP | KDDI Corporation |
| R2-2110333 | Discussion on support of inter-cell multi-TRP operation | Lenovo, Motorola Mobility |
| R2-2110341 | On Rel-17 FeMIMO | Ericsson |
| R2-2110435 | Considerations on Inter-cell Beam Management | CATT |
| R2-2110436 | Discussion on RRC Modeling of Inter-cell Beam Management | CATT |
| R2-2110534 | Considerations on Inter-Cell Beam Management | CMCC |
| R2-2110621 | Further Consideration on the beam managment for intra-cell mTRP | ZTE Corporation,Sanechips |
| R2-2110622 | Further Consideration on the inter-cell beam management | ZTE Corporation,Sanechips |
| R2-2110678 | Serving cell measurement for mTRP | Xiaomi Communications |
| R2-2110876 | Inter-cell beam management and inter-cell mTRP | Huawei, HiSilicon |
| R2-2110976 | Support of Inter-cell Beam Management and Multi-TRP | MediaTek Inc. |
| R2-2111141 | Inter-cell mTRP and inter-cell BM | LG Electronics |
| R2-2111205 | Inter-cell beam management and inter-cell mTRP | Huawei, HiSilicon |
| R2-2111325 | Summary of [AT116-e][015][feMIMO] Progressing FeMIMO (Nokia [lead], Ericsson, vivo) | Nokia (Rapporteur), Ericsson, vivo |
| 8.17.3 | Other | |
| R2-2109529 | Multi TRP Beam Failure Detection and Recovery | Samsung Electronics Co., Ltd |
| R2-2109642 | Remaining issues on mTRP BFR | Intel Corporation |
| R2-2109753 | RAN2 impacts of beam failure detection and recovery | Fujitsu |
| R2-2109760 | Discussion on RAN2 impacts of TRP-specific BFR | OPPO |
| R2-2110035 | User plane impact of inter-cell beam management | Apple |
| R2-2110036 | RAN2 impacts of beam failure detection and recovery | Apple |
| R2-2110334 | Beam failure recovery in multi-TRP | Lenovo, Motorola Mobility |
| R2-2110342 | RAN2 aspects for BFR, BFD and RLM for mTRP operation | Ericsson |
| R2-2110679 | Remaining issues of mTRP BFR | Xiaomi Communications |
| R2-2110748 | Discussion on multi-TRP BFR and new MIMO MAC CEs | Qualcomm Incorporated |
| R2-2110812 | Beam failure with mTRP | Nokia, Nokia Shanghai Bell |
| R2-2110877 | Beam failure recovery for multi-TRP | Huawei, HiSilicon |
| R2-2110962 | UL MAC CE enhancements for multi-TRP | Samsung |
| R2-2110985 | BFR handling on multiple TRP | LG Electronics Inc. |
| R2-2111206 | Beam failure recovery for multi-TRP | Huawei, HiSilicon |
| R2-2111284 | Summary of [AT116-e][016][feMIMO] MAC CE impacts (Samsung) | Samsung |
| R2-2111474 | Report of [AT116-e][017] [feMIMO] BFD BFR and Initial Running CRs (Samsung) | Samsung Electronics Co., Ltd |
| 8.18 | RACH indication and partitioning | |
| R2-2109572 | Discussion on general PRACH partition solution | OPPO |
| R2-2110037 | Common RACH Design | Apple |
| R2-2110270 | Report of [Post115-e][504][RACH Partitioning] Signalling Aspects (Ericsson) | Ericsson |
| R2-2110559 | RACH partitioning for Rel-17 features | Ericsson |
| 8.18.1 | Common signalling framework | |
| R2-2109442 | Discussion on RACH Partitioning in RA Configuration Aspect | vivo |
| R2-2109531 | Preamble and RACH resource configuration | Samsung Electronics Co., Ltd |
| R2-2109540 | Consideration on the common signalling framework for RACH partitioning | Beijing Xiaomi Software Tech |
| R2-2109881 | Support of RACH partitioning for multiple feature combinations | Intel Corporation |
| R2-2110439 | Discussion on RACH partitioning for feature combinations | CATT |
| R2-2110577 | Control plane aspects of RACH partitioning | ZTE Corporation, Sanechips |
| R2-2110597 | Common signalling for RACH indication and partitioning | Huawei, HiSilicon |
| R2-2110713 | RACH configuration signalling for Feature Combinations | Nokia, Nokia Shanghai Bell |
| R2-2111163 | Discussion on signalling aspects on RACH partitioning features | LG Electronics Inc. |
| 8.18.2 | Common aspects of RACH procedure | |
| R2-2109452 | Selection and fallback between RACH partitions | Qualcomm Incorporated |
| R2-2109532 | RA Procedure Aspects | Samsung Electronics Co., Ltd |
| R2-2109542 | Considerations on the common aspects of RACH procedure | Beijing Xiaomi Software Tech |
| R2-2109882 | RACH resource/configuration selection and fallback mechanism | Intel Corporation |
| R2-2110260 | Discussion on RACH indication and partitioning | CMCC |
| R2-2110560 | RNTI collision problem for Rel-17 features | Ericsson |
| R2-2110578 | User plane aspects of RACH partitioning | ZTE Corporation, Sanechips |
| R2-2110598 | MAC aspects for RACH partitioning | Huawei, HiSilicon |
| R2-2110665 | Overview of RACH resource selection | NEC |
| R2-2110813 | Selection of RACH partition | Nokia, Nokia Shanghai Bell |
| R2-2110917 | RACH indication and partitioning | InterDigital |
| R2-2110927 | Discussion on RACH Partitioning in RA Procedure Aspect | vivo |
| R2-2111164 | Discussion on common RA procedure for RACH partitioning features | LG Electronics Inc. |
| 8.19.1 | Organizational | |
| R2-2111210 | Reply LS on Msg3 repetition in coverage enhancement (R1-2110585; contact: ZTE) | RAN1 |
| 8.19.2 | General | |
| R2-2109443 | Further Discussion on RAN2 Impacts of Msg3 Repetition | vivo |
| R2-2109456 | RAN2 aspects of coverage enhancements | Qualcomm Incorporated |
| R2-2109503 | Discussion on CE’s impact on the start of ra-ContentionResolutionTimer | OPPO |
| R2-2109530 | MAC Aspects of UL Coverage Enhancements | Samsung Electronics Co., Ltd |
| R2-2109877 | RAN2 aspects of Msg3 PUSCH repetition | Intel Corporation |
| R2-2109894 | Consideration on Msg3 repetition in CE | ZTE Corporation, Sanechips |
| R2-2110038 | RAN2 impact of coverage enhancements | Apple |
| R2-2110192 | Considerations on requesting Msg3 repetition | NEC Corporation |
| R2-2110440 | Analysis on Type A PUSCH repetitions for Msg3 | CATT |
| R2-2110814 | RAN2 aspects for Coverage Enhancement | Nokia, Nokia Shanghai Bell |
| R2-2110833 | On Type A PUSCH repetitions for Msg3 | Ericsson |
| R2-2111026 | Further discussions on RAN2 support of Msg3 PUSCH repetition | Huawei, HiSilicon |
| R2-2111160 | Discussion on Msg3 PUSCH repetion | LG Electronics Inc. |
| R2-2111346 | [offline-112] Coverage Enhancements aspects | ZTE |
| 8.20.2 | General | |
| R2-2109444 | Discussion on Consistent LBT Failure Detection for Ext 71GHz | vivo |
| R2-2109604 | Discussion about RAN2 impacts of Ext 52-71GHz | Huawei, HiSilicon |
| R2-2109605 | Discussion about capability issues of Ext 52-71GHz | Huawei, HiSilicon |
| R2-2109883 | Further consideration of Capability differentiation between FR2-1 and FR2-2 | Intel Corporation |
| R2-2109884 | UP impact on NR operation for upto 71GHz | Intel Corporation |
| R2-2109909 | Aspects of CA operation and protocol impact | Ericsson |
| R2-2109910 | RRC impact due to FR2-1 and FR2-2 distinction | Ericsson |
| R2-2110016 | High layer impacts of beyond 52.6GHz | OPPO |
| R2-2110226 | Considerations on potential LBT impacts | Lenovo, Motorola Mobility |
| R2-2110338 | Discussion on L2 buffer size | Samsung |
| R2-2110339 | Impact of higher SCS on DRX parameters | Samsung |
| R2-2110362 | RA-RNTI and MsgB-RNTI calculations for FR2-2 | Sony |
| R2-2110557 | FR2-2 considerations | Nokia, Nokia Shanghai Bell |
| R2-2110581 | Discussion on UP impacts | ZTE Corporation, Sanechips |
| R2-2110582 | Higher SCS and RSSI impact on RRC | ZTE Corporation, Sanechips |
| R2-2111101 | Impact analysis of FR-2 on MAC and RRC | Qualcomm Incorporated |
| R2-2111158 | Consideration on L2 buffer size | LG Electronics Inc. |
| R2-2111159 | Consideration on potential LBT impact | LG Electronics Inc. |
| 8.21.1 | TEI proposals initiated by other groups | |
| R2-2110711 | Addition of Timing Advance measurement reporting in NR E-CID | Ericsson, NTT Docomo, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, CATT, Nokia, Nokia Shanghai Bell, Huawei |
| R2-2111213 | LS on NR Positioning support for TA measurement in NR UL E-CID (R1-2110601; contact: NTT DOCOMO) | RAN1 |
| 8.21.2 | TEI proposals initiated by RAN2 | |
| R2-2111537 | Report of [AT116-e][049][TEI17] TEI17 NR proposals (Chairman) | Chairman |
| 8.21.2.1 | CP centric | |
| R2-2109474 | UE assistance information configuration in RRCResume message | OPPO |
| R2-2109475 | Security algorithms update in RRC reestablishment message | OPPO |
| R2-2109716 | CR to 38.331 on support of NG-based (i.e. via CN) handover based using CGI report | China Telecom, Huawei, HiSilicon |
| R2-2109773 | Idle/Inactive state measurement enhancement for UEs supporting SUL | OPPO, Spreadtrum Communications, Qualcomm |
| R2-2110047 | User preferences to control location information sharing | Apple, Samsung, Google, Xiaomi, Vivo, BT Plc, Rakuten Mobile, MediaTek Inc |
| R2-2110055 | Discussion on Fast RLF recovery | Apple, Verizon |
| R2-2110056 | 38.331 CR to introduce fast RLF recovery (Option 1) | Apple, Verizon |
| R2-2110057 | 38.331 CR to introduce fast RLF recovery (Option 2) | Apple, Verizon |
| R2-2110198 | Fast Control of UL Skipping | NTT DOCOMO INC., Ericsson, CMCC, Verizon |
| R2-2110232 | Introduction of mobility-state-based cell reselection for NR HSDN | CMCC, CATT, Ericsson, Huawei, ZTE, OPPO, vivo |
| R2-2110233 | Introduction of mobility-state-based cell reselection for NR HSDN | CMCC, CATT, Ericsson, Huawei, ZTE, OPPO, vivo |
| R2-2110234 | Introduction of mobility-state-based cell reselection for NR HSDN | CMCC, CATT, Ericsson, Huawei, ZTE, OPPO, vivo |
| R2-2110235 | Introduction of mobility-state-based cell reselection for NR HSDN | CMCC, CATT, Ericsson, Huawei, ZTE, OPPO, vivo |
| R2-2110236 | Add the missing HSDN UE capability for LTE | CMCC, CATT, Ericsson, Huawei, ZTE, OPPO, vivo |
| R2-2110237 | Add the missing HSDN UE capability for LTE | CMCC, CATT, Ericsson, Huawei, ZTE, OPPO, vivo |
| R2-2110238 | Report for [Post115-e][090][TEI17] Mobility-state-based cell reselection for NR High Speed railway Dedicated Network | CMCC |
| R2-2110464 | PO determination in RRC_INACTIVE for Rel-17 and later releases | ZTE corporation, Sanechips, vivo |
| R2-2110465 | Text proposals for PO determination in RRC_INACTIVE | ZTE corporation, Sanechips, vivo |
| R2-2110485 | EPS fallback enhancements for UEs in IDLE/INACTIVE | Huawei, HiSilicon, CMCC, China Telecom, China Unicom, LG Uplus |
| R2-2110558 | RMSI alignment and HARQ granularity | Nokia, Nokia Shanghai Bell |
| R2-2110726 | On the need of providing explicit SI start position for SI Scheduling | Ericsson, Verizon, Deutsche Telekom, Softbank, Swift Navigation, ESA |
| R2-2110772 | Introduction of mobility-state-based cell reselection for NR HSDN | CMCC |
| R2-2110799 | SIB and posSIB scheduling constraints | MediaTek Inc. |
| R2-2110836 | Periodic SRS in SCell dormant BWP | Qualcomm Incorporated, ZTE Corporation, Futurewei |
| R2-2110838 | [gNB_ID_Length] On the inclusion of gNB ID length in the NR CGI report | Ericsson, Verizon Wireless, Telus Mobility, Bell Mobility |
| R2-2110839 | [gNB_ID_Length] On the inclusion of gNB ID length in the NR CGI report | Ericsson, Verizon Wireless, Telus Mobility, Bell Mobility |
| R2-2110840 | [gNB_ID_Length] On the inclusion of gNB ID length in the NR CGI report | Ericsson, Verizon Wireless, Telus Mobility, Bell Mobility |
| R2-2110841 | [gNB_ID_Length] On the inclusion of gNB ID length in the NR CGI report | Ericsson, Verizon Wireless, Telus Mobility, Bell Mobility |
| R2-2110842 | [gNB_ID_Length] On the inclusion of gNB ID length in the NR CGI report | Ericsson, Verizon Wireless, Telus Mobility, Bell Mobility |
| R2-2110844 | [gNB_ID_Length] On the inclusion of gNB ID length in the NR CGI report | Ericsson, Verizon Wireless, Telus Mobility, Bell Mobility |
| R2-2110845 | Configuration of chronological order for performing inter-frequency measurements | Ericsson, Vodafone |
| R2-2110847 | On broadcasting gNB ID length in system information block and associated CGI reporting (reply to RAN3 LS R3-212966) | Ericsson, Verizon Wireless, Bell Mobility, Telus Mobility |
| R2-2110856 | On using RAN3 based solution for unsupported SCS+BW of neighbor cell | Ericsson |
| R2-2110857 | [Draft] Reply LS on broadcasting gNB ID length in system information block | Ericsson |
| R2-2110981 | On the support of NG-based handover using CGI report | Huawei, HiSilicon, CMCC, China Telecom, China Unicom |
| R2-2111091 | Early measurement for EPS Fallback and Load Distribution | vivo, China Telecom, CMCC, SoftBank, NTT DOCOMO INC, China Unicom, Ericsson vodafone |
| R2-2111092 | 38331 CR for Early measurement for EPS Fallback and Load Distribution | vivo, China Telecom, CMCC, SoftBank, NTT DOCOMO INC, China Unicom, Ericsson vodafone |
| R2-2111093 | 38306 CR for Early measurement for EPSFallback Load Distribution | vivo, China Telecom, CMCC, SoftBank, NTT DOCOMO INC, China Unicom, Ericsson vodafone |
| R2-2111161 | Skipping RACH upon data arrival | NTT DOCOMO, INC. |
| R2-2111193 | Discussion on early identification of Emergency Call | RadiSys, Reliance JIO |
| R2-2111248 | On the need of providing explicit SI start position for SI Scheduling | Ericsson, Verizon, Deutsche Telekom, Softbank, Swift Navigation, ESA, T-Mobile USA |
| R2-2111261 | Discussion on Fast RLF recovery | Apple, Verizon, Xiaomi |
| R2-2111269 | Discussion on early identification of Emergency Call | RadiSys, Reliance JIO, Verizon, Peraton Labs |
| R2-2111270 | Configuration of chronological order for performing inter-frequency measurements | Ericsson, Vodafone, T-Mobile |
| R2-2111279 | Add the missing HSDN UE capability for LTE | CMCC, CATT, Ericsson, Huawei, ZTE, OPPO, vivo |
| R2-2111280 | Add the missing HSDN UE capability for LTE | CMCC, CATT, Ericsson, Huawei, ZTE, OPPO, vivo |
| R2-2111555 | Report of [AT116-e][039][TEI17] PO determination in RRC_INACTIVE (ZTE) | ZTE corporation, Sanechips |
| R2-2111556 | Correction on PO determination for UE in inactive state | ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Sanechips |
| R2-2111557 | Correction on PO determination for UE in inactive state | ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Sanechips |
| R2-2111558 | Correction on PO determination for UE in inactive state | ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Sanechips |
| R2-2111559 | Correction on PO determination for UE in inactive state | ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Sanechips |
| R2-2111560 | Correction on PO determination for UE in inactive state | ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Sanechips |
| R2-2111561 | Correction on PO determination for UE in inactive state | ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Sanechips |
| R2-2111584 | Correction on PO determination for UE in inactive state | ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Sanechips |
| R2-2111585 | Correction on PO determination for UE in inactive state | ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Sanechips |
| R2-2111586 | Correction on PO determination for UE in inactive state | ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Sanechips |
| R2-2111587 | Correction on PO determination for UE in inactive state | ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Sanechips |
| R2-2111588 | Correction on PO determination for UE in inactive state | ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Sanechips |
| R2-2111589 | Correction on PO determination for UE in inactive state | ZTE corporation, Ericsson, vivo, CMCC, China Telecom, China Unicom, Sanechips |
| 8.21.2.2 | UP centric | |
| R2-2109651 | Handling of pending empty PDUs after UCI multiplexing | CATT, Lenovo, Motorola Mobility |
| R2-2109652 | Enabling Multi-TB CGs on licensed bands | CATT |
| R2-2109730 | C-DRX enhancements for 5G applications | vivo, CMCC, China Telecom, China Unicom, Spreadtrum, Guangdong Genius |
| R2-2109851 | Adaptation of QoS Flow to DRB Mapping for MDBV Enforcement | Futurewei |
| R2-2109852 | Activation/Deactivation of QoS Flow to DRB Mapping for SMBR Enforcement | Futurewei |
| R2-2109951 | User Plane Improvements | Nokia, Nokia Shanghai Bell |
| R2-2110070 | SDAP end-marker in RLC UM | Apple, Futurewei, Spreadtrum, FGI, Asia Pacific Telecom |
| R2-2110417 | Secondary DRX enhancements | Ericsson, Verizon, Qualcomm Inc |
| R2-2110759 | Efficient UL pre-scheduling operation | MediaTek Inc., Qualcomm Inc. |
| R2-2111170 | Stopping CGT for ignored or skipped UL grant | LG Electronics Inc. |
| R2-2111172 | CR to 38321 on stopping CGT for ignored or skipped UL grant | LG Electronics Inc. |
| R2-2111229 | Secondary DRX enhancements | Ericsson, Verizon, Qualcomm Inc, T-Mobile USA Inc. |
| R2-2111460 | Secondary DRX enhancements | Verizon, Ericsson, Qualcomm Inc, T-Mobile USA Inc., Deutsche Telecom |
| 8.22 | NR and MR-DC measurement gap enhancements | |
| R2-2109361 | LS on R17 NR MG enhancements – Concurrent MG (R4-2115343; contact: CATT & MediaTek) | RAN4 |
| R2-2109367 | LS on R17 NR MG enhancements – Pre-configured MG (R4-2115438; contact: Huawei & vivo) | RAN4 |
| R2-2109694 | Consideration on NR and MR-DC MG enhancements | CATT |
| R2-2109695 | [Draft] Reply LS on R17 NR MG enhancements – Concurrent MG | CATT |
| R2-2109731 | Discussion on per-configured measurement gap | vivo |
| R2-2109754 | Discussion on multiple concurrent and independent MG patterns | vivo |
| R2-2109789 | Multiple concurrent and independent measurement gap patterns | Samsung |
| R2-2109790 | Preconfigured measurement gap patterns | Samsung |
| R2-2109875 | Measurement gap enhancement for pre-configured gap | Intel Corporation |
| R2-2109876 | Measurement gap enhancement for concurrent gap | Intel Corporation |
| R2-2109895 | Consideration on pre-configured measurement gap | ZTE Corporation, Sanechips |
| R2-2109896 | Consideration on concurrent measurement gap | ZTE Corporation, Sanechips |
| R2-2110077 | RAN2 impact from Rel-17 measurement gap enhancement | Apple |
| R2-2110139 | Discussion on Pre-configured MG | OPPO |
| R2-2110140 | Discussion on Concurrent MG | OPPO |
| R2-2110278 | Discussion on Pre-configured MG | Huawei, HiSilicon |
| R2-2110279 | Discussion on Concurrent MG | Huawei, HiSilicon |
| R2-2110280 | Discussion on the configuration of NCSG | Huawei, HiSilicon |
| R2-2110383 | Measurement gap enhancements | LG Electronics Inc. |
| R2-2110707 | On support of Concurrent MG enhancement | Nokia, Nokia Shanghai Bell |
| R2-2110708 | On support of Pre-configured MG enhancement | Nokia, Nokia Shanghai Bell |
| R2-2110905 | Pre-configured measurement gaps | Ericsson |
| R2-2110906 | Concurrent measurement gaps | Ericsson |
| R2-2110944 | RAN2 protocol impacts on preconfigured Measurement Gap | DENSO CORPORATION |
| R2-2111152 | Signalling design on concurrent gaps | DENSO CORPORATION |
| R2-2111184 | Work plan of R17 NR and MR-DC measurement gap enhancements WI | MediaTek (Rapporteur), Intel (Rapporteur) |
| R2-2111187 | Discussion on RAN2 impacts for MG enhancement WI | MediaTek Inc. |
| R2-2111189 | RRC signaling for measurement gap enhancement | MediaTek Inc. |
| R2-2111254 | RAN2 impact from Rel-17 measurement gap enhancement | Apple |
| R2-2111471 | Report of [AT116-e][041][MGE] Concurrent MG (MediaTek) | MediaTek |
| R2-2111472 | Reply LS on R17 NR MG enhancements – Concurrent MG | RAN2 |
| R2-2111517 | Pre-Configured MG (Intel) | Intel (Rapporteur) |
| R2-2111518 | Draft] Clarification for Pre-configured MG | Intel |
| R2-2111541 | [Draft] Clarification for Pre-configured MG | Intel |
| R2-2111598 | [draft] Reply LS on Pre-configured MG | Intel Corporation |
| R2-2111601 | Reply LS on Pre-configured MG | RAN2 |
| 8.23 | Uplink Data Compression (UDC) | |
| R2-2111066 | Work plan for NR UDC | CATT |
| R2-2111067 | Discussion on introduction of NR UDC | CATT, CMCC, Huawei, HiSilicon, MediaTek |
| 8.24.1 | RAN4 led Items | |
| R2-2109353 | LS on specification impact for methods on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths (R4-2114751; contact: Nokia) | RAN4 |
| R2-2109354 | LS on signalling for intra-band CA with UL-MIMO (R4-2114754; contact: OPPO) | RAN4 |
| R2-2109355 | LS on signaling for power class 1.5 (R4-2114929; contact: Qualcomm) | RAN4 |
| R2-2109356 | LS on UE capability for UE power class 2 NR inter-band CA and SUL configurations (R4-2114933; contact: China Telecom) | RAN4 |
| R2-2109358 | LS on UL gap in FR2 RF enhancement (R4-2114965; contact: Apple) | RAN4 |
| R2-2109359 | Reply LS to RAN2 on the capability of transparent TxD (R4-2115111; contact: vivo) | RAN4 |
| R2-2109360 | LS on beam information of PUCCH SCell in PUCCH SCell activation procedure (R4-2115339; contact: Huawei) | RAN4 |
| R2-2109393 | Discussion on MIMO-dependent bandwidth class and frequency separation | OPPO, Ericsson, ZTE Corporation, Sanechips |
| R2-2109394 | Reply LS on signalling for intra-band CA with UL-MIMO | OPPO |
| R2-2109566 | Discussion on CSI report for being activated PUCCH SCell | OPPO |
| R2-2109569 | Draft LS on CSI report of PUCCH SCell | OPPO |
| R2-2109570 | Discussion on UL gap pattern for FR2 TX power management | OPPO |
| R2-2109571 | Draft LS on UL gap for FR2 TX power management | OPPO |
| R2-2109659 | Draft CR on CSI report of PUCCH SCell | OPPO |
| R2-2109732 | CR on 38.306 for the capability of supporting txDiversity | vivo |
| R2-2109733 | CR on 38.331 for the capability of supporting txDiversity | vivo |
| R2-2109794 | Flexible bandwidth utilization | Nokia, Nokia Shanghai Bell |
| R2-2109795 | Reply LS on flexibile bandwidth utilization | Nokia, Nokia Shanghai Bell |
| R2-2109796 | Duty cycle signalling for power class 1.5 | Nokia, Nokia Shanghai Bell |
| R2-2109797 | Duty cycle signalling for power class 1.5 | Nokia, Nokia Shanghai Bell |
| R2-2109798 | UL gaps for FR2 | Nokia, Nokia Shanghai Bell |
| R2-2109799 | UE capability for UE power class 2 NR inter-band CA and SUL configurations | Nokia, Nokia Shanghai Bell |
| R2-2109889 | Discussion on irregular bandwidth | ZTE Corporation, Sanechips |
| R2-2109890 | Reply LS on irregular bandwidth | ZTE Corporation, Sanechips |
| R2-2110076 | RAN2 impact from UL gap in FR2 RF enhancement | Apple |
| R2-2110086 | Discussion on irregular channel bandwidth LS from RAN4 | Apple |
| R2-2110087 | [Draft] reply LS on irregular channel bandwidth feature | Apple |
| R2-2110088 | Discussion on LS reply for PUCCH Scell | Apple |
| R2-2110089 | [Draft] LS reply for PUCCH Scell RAN4 LS | Apple |
| R2-2110387 | Consideration on the BCS4/5 Supporting | ZTE Corporation, Sanechips |
| R2-2110424 | Running CR to TS 38.306 to support Tx switching enhancements | China Telecom, Huawei, HiSilicon, Apple, CATT |
| R2-2110425 | CR to TS 38.306 on UE capability for UE power class 2 NR inter-band CA and SUL configurations | China Telecom, Huawei, HiSilicon |
| R2-2110426 | CR to TS 38.331 on UE capability for UE power class 2 NR inter-band CA and SUL configurations | China Telecom, Huawei, HiSilicon |
| R2-2110486 | Discussion on beam information of PUCCH SCell in PUCCH SCell activation (RAN4 LS) | Huawei, HiSilicon |
| R2-2110487 | Draft LS Reply on beam information of PUCCH SCell in PUCCH SCell activation procedure | Huawei, HiSilicon |
| R2-2110491 | Discussion on RAN4 LS regarding methods on efficient utilization of licensed spectrum | vivo |
| R2-2110512 | Introduction of BCS4 and BCS5 | Qualcomm Incorporated |
| R2-2110787 | Specification impact for methods on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths | Ericsson |
| R2-2110964 | [DRAFT] LS Reply on beam information of PUCCH SCell in PUCCH SCell activation procedure | Samsung |
| R2-2110974 | Discussion on 100M bandwidth capability for Rel-17 | Huawei, HiSilicon |
| R2-2111035 | PUCCH SCell activation | Nokia, Nokia Shanghai Bell |
| R2-2111055 | CR on 38.331 for introducing UE capability of txDiversity | CMCC |
| R2-2111056 | CR on 38.306 for introducing UE capability of txDiversity | CMCC |
| R2-2111059 | RAN2 signalling to support R17 UL Tx switching enhancements | Huawei, HiSilicon, China Telecom, Apple |
| R2-2111060 | RRC configuration to support R17 UL Tx switching enhancements | Huawei, HiSilicon, China Telecom, Apple |
| R2-2111061 | Running CR to TS38.331 to support Tx switching enhancements | Huawei, HiSilicon, China Telecom, Apple, CATT |
| R2-2111153 | On efficient utilization of irregular spectrum | Huawei, HiSilicon |
| R2-2111209 | Reply LS on specification impact for methods on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths (R1-2110584; contact: Nokia) | RAN1 |
| R2-2111218 | Reply LS on SCell dropping issue of CA (R1-2110660; contact: Huawei) | RAN1 |
| R2-2111322 | Summary of [AT116-e][022][NR17] Irregular BW (Nokia) | Nokia (Rapporteur) |
| R2-2111456 | Phase 1 summary of [AT116-e][023][NR17] FR2 UL Gap (Apple) | Apple |
| R2-2111461 | Summary of offline [AT116-e][024][NR17] BCS4/5 (ZTE) | ZTE |
| R2-2111464 | Summary of [AT116-e][020][NR17] MIMO-dependent BW class (OPPO) | OPPO |
| R2-2111465 | Reply LS on signalling for intra-band CA with UL-MIMO | RAN2 |
| R2-2111469 | Summary of [AT116-e][018][NR17] Beam information of PUCCH SCell in PUCCH SCell activation (Huawei) | Huawei, HiSilicon |
| R2-2111498 | Summary of [AT116-e][021][NR17] Power Class (Qualcomm, China Telecom) | China Telecom |
| R2-2111499 | CR to TS 38.306 on UE capability for UE power class 2 NR inter-band CA and SUL configurations | China Telecom, Huawei, HiSilicon |
| R2-2111502 | CR on 38.331 for introducing UE capability of txDiversity | CMCC, CATT, China Telecom, China Unicom, Huawei, HiSilicon, OPPO, vivo |
| R2-2111503 | CR on 38.306 for introducing UE capability of txDiversity | CMCC, CATT, China Telecom, China Unicom, Huawei, HiSilicon, OPPO, vivo |
| R2-2111529 | Duty cycle signalling for power class 1.5 | Nokia, Nokia Shanghai Bell |
| R2-2111530 | Duty cycle signalling for power class 1.5 | Nokia, Nokia Shanghai Bell |
| R2-2111573 | Summary of offline discussion #019: TX Diversity(vivo) | vivo |
| R2-2111575 | Reply LS to RAN4 on UL gap in FR2 RF enhancement | RAN2 |
| R2-2111578 | Summary of [AT116-e] [025][NR17] UL TX Switching & 100M BW (Huawei) | Huawei, HiSilicon |
| R2-2111597 | Reply LS on specification impact for methods on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths | RAN2 |
| 8.24.2 | RAN1 led Items | |
| R2-2109332 | LS on Cross-carrier scheduling from SCell to P(S)Cell (R1-2108662; contact: Ericsson) | RAN1 |
| R2-2109953 | Cross-carrier scheduling from SCell to P(S)Cell | Nokia (Rapporteur) |
| R2-2110507 | Discussion on Cross-Carrier Scheduling from sSCell to P(S)Cell | vivo |
| R2-2110729 | stage2 38.300 running CR for DSS | Ericsson |
| R2-2110730 | RRC running CR for DSS | Ericsson |
| R2-2110731 | RAN2 impact in DSS WI | Ericsson |
| R2-2111025 | Considerations on cross-carrier scheduling from SCell to P(S)Cell | Huawei, HiSilicon |
| R2-2111459 | Summary of [AT116-e][026][NR17] DSS (Ericsson) | Ericsson |
| R2-2111542 | 38.300 running CR for DSS | Ericsson |
| 8.24.3 | Other | |
| R2-2109816 | Reply LS on UAC enhancements for minimization of service interruption when disaster condition applies (C1-216253; contact: Ericsson) | CT1 |
| R2-2109818 | LS on system information extensions for minimization of service interruption (MINT) (C1-216297; contact: Ericsson) | CT1 |
| R2-2109834 | Selection of MINT UAC solution | Lenovo, Motorola Mobility |
| R2-2109835 | Discussion on system information extensions for MINT | Lenovo, Motorola Mobility |
| R2-2110681 | RAN2 aspects for MINT | Ericsson |
| R2-2111146 | RAN2 impact for supporting disaster roaming | LG Electronics |
| R2-2111147 | Text proposal to 38.331 for solution 38 and 40 | LG Electronics |
| R2-2111224 | RAN2 impact from MINT | Apple |
| R2-2111243 | LS on MINT functionality for Disaster Roaming (S2-2108172; contact: LGE) | SA2 |
| R2-2111258 | LS on question and feedback about the EVEX Work Item (C3-215316; contact: Ericsson) | CT3 |
| R2-2111550 | Introduction of MINT | Ericsson |
| R2-2111551 | Introduction of MINT | Ericsson |
| R2-2111552 | Introduction of MINT | Ericsson |
| R2-2111553 | Introduction of MINT | RAN2 |
| R2-2111554 | Reply LS on UAC enhancements for minimization of service interruption when disaster condition applies | Ericsson |
| R2-2111571 | Summary of [AT116-e][053][NR17] MINT (Ericsson) | Ericsson |
| R2-2111599 | Reply LS on UAC enhancements and system information extensions for minimization of service interruption | RAN2 |
| 9.1.1 | Organizational | |
| R2-2110477 | Running CR: Introduction of Rel-17 enhancements for NB-IoT and eMTC | Huawei |
| R2-2110692 | [Running CR] Introduction of NB-IoT/eMTC Enhancements | Qualcomm Incorporated |
| R2-2111396 | RAN2 agreements for Rel-17 NB-IoT and LTE-MTC | Ericsson |
| 9.1.2 | NB-IoT neighbor cell measurements and corresponding measurement triggering before RLF | |
| R2-2109913 | Discussion on connected mode measurement in NB-IoT | Ericsson |
| R2-2110109 | Remaining FFSs on RLF measurements | ZTE Corporation, Sanechips |
| R2-2110147 | Network assistance for Re-establishment enhancement | Nokia, Nokia Shanghai Bells |
| R2-2110474 | Relaxed monitoring in RRC connected mode | Huawei, HiSilicon |
| R2-2110476 | Summary of [301] RLF measurements (Huawei) | Huawei |
| R2-2110693 | Consideration on open issues for neighbour cell measurement in RRC connected state | Qualcomm Incorporated |
| R2-2111393 | Report of [AT116e][303][NBIOT/eMTC] RLF measurements (Qualcomm) | Qualcomm Incorporated |
| 9.1.3 | NB-IoT carrier selection based on the coverage level, and associated carrier specific configuration | |
| R2-2109911 | Report of email discussion [302] [NBIOT/eMTC R17] Carrier Selection | Ericsson |
| R2-2109912 | Analysis of Rmax based solution and carrier-based solution | Ericsson |
| R2-2110110 | Option1c for CEL-based paging carrier selection | ZTE Corporation, Sanechips |
| R2-2110148 | Paging strategy impacts for coverage based paging carrier selection | Nokia, Nokia Shanghai Bells |
| R2-2110149 | Network configuration for paging carrier selection based on coverage level | Nokia, Nokia Shanghai Bells |
| R2-2110191 | Further discussion on enhanced paging carrier selection | NEC Corporation |
| R2-2110475 | Discussion on coverage based paging carrier | Huawei, HiSilicon |
| R2-2110694 | Further consideration on open issues for coverage-based paging carrier selection | Qualcomm Incorporated |
| R2-2110695 | Signalling for coverage-based paging carrier selection | Qualcomm Incorporated |
| R2-2111113 | Discussion on details of paging carrier selection options | MediaTek Inc. |
| R2-2111394 | Report of [AT116-e][304][NBIOT/eMTC] NB-IoT carrier selection (ZTE) | ZTE (email discussion rapporteur) |
| 9.1.4 | Other | |
| R2-2109914 | Support of 16-QAM for unicast in UL and DL in NB-IoT | Ericsson |
| R2-2110111 | Remaining FFSs on 16QAM for NB-IoT | ZTE Corporation, Sanechips |
| R2-2110112 | Remaining FFSs on 1736bits TBS for eMTC | ZTE Corporation, Sanechips |
| R2-2110473 | L2 buffer size calculations for eMTC and NB-IoT enhancements | Huawei, HiSilicon |
| R2-2110800 | On remaining issues of 16QAM | Nokia Solutions & Networks (I) |
| 9.2.1 | Organizational | |
| R2-2110478 | Running CR - Support of Non-Terrestrial Network in NB-IoT and eMTC | Huawei |
| R2-2111212 | LS on Validity Timer for UL Synchronization (R1-2110673; contact: Ericsson) | RAN1 |
| R2-2111245 | Reply LS on EPS support for IoT NTN in Rel-17 (S2-2108176; contact: MediaTek) | SA2 |
| R2-2111405 | NB-IoT/eMTC support for Non-Terrestrial Networks [Stage 2 Running CR] | Eutelsat |
| R2-2111436 | Running CR - Support of Non-Terrestrial Network in NB-IoT and eMTC | Huawei |
| R2-2111631 | 36304 Running CR for IoT NTN | Ericsson |
| R2-2111647 | Stage-3 running CR for TS 36.321 for Rel-17 IoT-NTN | MediaTek |
| 9.2.2 | Support of Non continuous coverage | |
| R2-2109504 | Discussion on discontinuous coverage for IoT over NTN | OPPO |
| R2-2109640 | Discussion on remaining issues on non-continuous coverage | Intel Corporation |
| R2-2109702 | Discussion on the support of discontinuous coverage for IoT NTN | CATT |
| R2-2109821 | Contents and delivery options for Satellite Assistance Information for NTN | Gatehouse, Sateliot |
| R2-2109965 | Satellite visit time for non-continuous coverage | Qualcomm Incorporated |
| R2-2110071 | Support of discontinuous coverage | Apple |
| R2-2110114 | Remaining FFSs on discontinuous coverage in IoT NTN | ZTE Corporation, Sanechips |
| R2-2110130 | Discussion on the issue of non-continuous coverage | Spreadtrum Communications |
| R2-2110262 | Discussion on support of Non continuous coverage | CMCC |
| R2-2110313 | Assistance information for NTN discontinuous coverage | Lenovo, Motorola Mobility |
| R2-2110314 | Enhancement for idle UE power saving in discontinuous coverage | Lenovo, Motorola Mobility |
| R2-2110315 | RRC connection handling for discontinuous coverage in IoT NTN | Lenovo, Motorola Mobility |
| R2-2110544 | Power Saving in Discontinuous Coverage for NB IoT NTN | Rakuten Mobile, Inc |
| R2-2110549 | Support of Discontinuous Coverage for IoT-NTN | Interdigital, Inc. |
| R2-2110705 | On aspects of discontinuous coverage in IoT NTN | Nokia, Nokia Shanghai Bell |
| R2-2110834 | Discontinuous coverage in IoT NTN | Ericsson |
| R2-2110922 | On Discontinuous coverage in IoT-NTN | MediaTek Inc. |
| R2-2110977 | Discussion on non continuous coverage | Huawei, HiSilicon |
| R2-2111112 | Discussion on discontinuous coverage | Xiaomi |
| R2-2111479 | Summary of 9.2.2 Non continuous coverage | MediaTek Inc. |
| 9.2.3 | User Plane Impact | |
| R2-2109505 | Discussion on UP impact for IoT over NTN | OPPO |
| R2-2109701 | Discussion on TA information reporting for IoT NTN | CATT |
| R2-2109966 | UL synchronization validity timer in RRC_CONNECTED | Qualcomm Incorporated |
| R2-2110115 | Remaining FFSs on UP in IoT NTN | ZTE Corporation, Sanechips |
| R2-2110268 | Discussion on UP aspects for IoT-NTN | CMCC |
| R2-2110479 | User plane for IOT NTN | Huawei, HiSilicon |
| R2-2110550 | IoT-NTN UP impacts | Interdigital, Inc. |
| R2-2110706 | On User Plane aspects for IoT NTN | Nokia, Nokia Shanghai Bell |
| R2-2110919 | Validity Timer Expiry and Synchronization Loss in IoT-NTN | MediaTek Inc. |
| R2-2110953 | User plane aspects of NB-IoT and LTE-M in NTNs | Ericsson |
| R2-2111477 | Report of [AT116-e][028][IoT-NTN] User Plane Impact (OPPO) | OPPO |
| 9.2.4 | Control Plane Impact | |
| R2-2109506 | Discussion on CP impact for IoT over NTN | OPPO |
| R2-2109633 | On Soft-switch based Tracking Area Updates in IoT-NTN | MediaTek Inc. |
| R2-2109703 | Discussion on the mobility issues of IoT NTN | CATT |
| R2-2109923 | On Cell Re-selection in IoT-NTN | MediaTek Inc. |
| R2-2109967 | GNSS fix and Paging response delay | Qualcomm Incorporated |
| R2-2110020 | Consideration on RRC release for IOT NTN | Beijing Xiaomi Mobile Software |
| R2-2110072 | Provision of ephemeris | Apple |
| R2-2110113 | Remaining FFSs on CP in IoT NTN | ZTE Corporation, Sanechips |
| R2-2110146 | Further discussion on TA switching and Idle mode procedures for IoT-NTN | Nokia, Nokia Shanghai Bells |
| R2-2110480 | Control plane for IOT NTN | Huawei, HiSilicon |
| R2-2110551 | IoT-NTN cell change | Interdigital, Inc. |
| R2-2110561 | PRACH Congestion mitigation in NTN IoT | Rakuten Mobile, Inc |
| R2-2110770 | Analysis on Mobility Aspects for IoT NTN | NEC Telecom MODUS Ltd. |
| R2-2110835 | Control plane aspects of IoT NTN | Ericsson |
| R2-2111030 | Discussion on control plane issues for IoT NTN | Xiaomi Communications |
| R2-2111045 | Discussion on CP Impact for IoT over NTN | CMCC |
| R2-2111475 | [AT116-e][030][IoT-NTN] CP Other (Huawei) | Huawei |
| R2-2111516 | Report of [Offline-029][IoT-NTN] Idle mode mobility and TA handling | Ericsson |
| 9.3 | EUTRA R17 Other | |
| R2-2109377 | LS Reply on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS (S2-2106974; contact: Huawei) | SA2 |
| R2-2109379 | LS on User Plane Integrity Protection for eUTRA connected to EPC (S3-213272; contact: Qualcomm) | SA3 |
| R2-2109715 | Introduction of event-based trigger for LTE MDT logging | KDDI Corporation, CMCC, Telecom Italia, Samsung, Ericsson, China Unicom, Huawei, HiSilicon, Qualcomm Inc. |
| R2-2109717 | Introduction of event-based trigger for LTE MDT logging | KDDI Corporation, CMCC, Telecom Italia, Samsung, Ericsson, China Unicom, Huawei, HiSilicon, Qualcomm Inc. |
| R2-2109718 | UE’s height location measurement for LTE MDT | KDDI Corporation, Ericsson, China Unicom, Samsung, Qualcomm Inc. |
| R2-2109924 | [Post115-e][203][TEI] Discussion on details of event-triggered logged MDT for LTE | Qualcomm Incorporated |
| R2-2110080 | Addition of NR-U RSSI/CO measurement UE capability | Apple, xiaomi, vivo |
| R2-2110081 | Addition of NR-U RSSI/CO measurement UE capability | Apple, xiaomi, vivo |
| R2-2110643 | Introduction of event-based trigger for LTE MDT logging | Huawei, HiSilicon, Qulacomm Inc., KDDI Corporation |
| R2-2110644 | Introduction of event-based trigger for LTE MDT logging | Huawei, HiSilicon, Qualcomm Inc., KDDI Corporation |
| R2-2111260 | UE’s height location measurement for LTE MDT | KDDI Corporation, Ericsson, China Unicom, Samsung, Qualcomm Inc., Telecom Italia |
| R2-2111319 | Addition of NR-U RSSI/CO measurement UE capability | Apple, xiaomi, vivo |
| R2-2111320 | Addition of NR-U RSSI/CO measurement UE capability | Apple, xiaomi, vivo |
| R2-2111321 | Introduction of event-based trigger for LTE MDT logging | KDDI Corporation, CMCC, Telecom Italia, Samsung, Ericsson, China Unicom, Huawei, HiSilicon, Qualcomm Inc. |
| R2-2111326 | Introduction of event-based trigger for LTE MDT logging | KDDI Corporation, CMCC, Telecom Italia, Samsung, Ericsson, China Unicom, Huawei, HiSilicon, Qualcomm Inc. |
| R2-2111327 | Introduction of event-based trigger for LTE MDT logging | KDDI Corporation, CMCC, Telecom Italia, Samsung, Ericsson, China Unicom, Huawei, HiSilicon, Qualcomm Inc. |
| R2-2111462 | Addition of NR-U RSSI/CO measurement UE capability | Apple, xiaomi, vivo |
| R2-2111463 | Addition of NR-U RSSI/CO measurement UE capability | Apple, xiaomi, vivo |
| 9.4 | NR and EUTRA Inclusive language | |
| R2-2109338 | Reply LS on Inclusive Language for ANR (R3-214289; contact: Ericsson) | RAN3 |
| R2-2109357 | LS on Inclusive Language Review Status and Consistency Check (R4-2115067; contact: Ericsson) | RAN4 |
| 10.1 | Session on LTE legacy, Mobility, DCCA, Multi-SIM and RAN slicing | |
| R2-2111291 | Report from session on LTE legacy, 71 GHz, DCCA, Multi-SIM and RAN slicing | Vice Chairman (Nokia) |
| 10.2 | Session on R17 NTN and RedCap | |
| R2-2111292 | Report from Break-Out Session on R17 NTN, RedCap and CE | ZTE Corporation |
| 10.3 | Session on eMTC | |
| R2-2111293 | Report eMTC breakout session | Session chair (Ericsson) |
| 10.4 | Session on R17 Small data and URLLC/IIOT | |
| R2-2111294 | Report for Rel-17 Small data and URLLC/IIoT | Session chair (InterDigital) |
| 10.5 | Session on positioning and sidelink relay | |
| R2-2111295 | Report from session on positioning and sidelink relay | Session chair (MediaTek) |
| 10.6 | Session on SON/MDT | |
| R2-2111296 | Report from SOM/MDT session | Session chair (CMCC) |
| 10.7 | Session on NB-IoT | |
| R2-2111297 | Report NB-IoT breakout session | Session chair (InterDigital) |
| 10.8 | Session on LTE V2X and NR SL | |
| R2-2111298 | Report from session on LTE V2X and NR SL | Session chair (Samsung) |